Linux

48209 readers

958 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

What Filesystem? (self.linux)

submitted 1 year ago by cianmor to c/[email protected]

119 comments fedilink hide all child comments

What filesystem is currently best for a single nvme drive with regard to performance read/write as well as stability/no file loss? ext4 seems very old, btrfs is used by RHEL, ZFS seems to be quite good... what do people tend to use nowadays? What is an arch users go-to filesystem?

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 1 year ago (1 children)

First of all, thanks this r news for me. But I don't think is a good idea to use the swap file in btrfs.

It is supported since kernel 5.0

There are some limitations of the implementation in BTRFS and Linux swap subsystem:

filesystem - must be only single device

filesystem - must have only single data profile

subvolume - cannot be snapshotted if it contains any active swapfiles

swapfile - must be preallocated (i.e. no holes)

swapfile - must be NODATACOW (i.e. also NODATASUM, no compression)

With active swapfiles, the following whole-filesystem operations will skip swapfile extents or may fail:

balance - block groups with extents of any active swapfiles are skipped and reported, the rest will be processed normally

resize grow - unaffected

resize shrink - works as long as the extents of any active swapfiles are outside of the shrunk range

device add - if the new devices do not interfere with any already active swapfiles this operation will work, though no new swapfile can be activated afterwards

device delete - if the device has been added as above, it can be also deleted

device replace - ditto

[–] [email protected] 1 points 1 year ago

Yes, there are some limitations to be aware of, with how it interacts with certain features. But EXT4 doesn't have any of those features at all. It doesn't have CoW, or balance, or multi-device, or snapshots.

If the filesystem, is single-device, and you have the swapfile on it's own nocow subvolume, preallocate the swapfile, and don't try to take snapshots of it, it should be fine.