this post was submitted on 24 Aug 2024
232 points (100.0% liked)

Linux

1253 readers
66 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

Related Communities

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

founded 5 years ago
MODERATORS
 

There's been some Friday night kernel drama on the Linux kernel mailing list... Linus Torvalds has expressed regrets for merging the Bcachefs file-system and an ensuing back-and-forth between the file-system maintainer.

you are viewing a single comment's thread
view the rest of the comments
[–] DaPorkchop_@lemmy.ml 47 points 1 month ago (2 children)

ext4 is intended for a completely different use case, though? bcachefs is competing with btrfs and ZFS in big storage arrays spanning multiple drives, probably with SSD cache. ext4 is a nice filesystem for client devices, but doesn't support some things which are kinda fundamental at larger scales like data checksumming, snapshots, or transparent compression.

[–] GolfNovemberUniform@lemmy.ml 6 points 1 month ago (3 children)

There's XFS for larger scale stuff.

[–] DaPorkchop_@lemmy.ml 26 points 1 month ago

XFS still isn't a multi-device filesystem, though... of course you can run it on top of mdraid/LVM, but that still doesn't come close to the flexibility of what these specialized filesystems can do. Being able to simply run btrfs device add /dev/sdx1 / and immediately having the new space available is far less hassle than adding a device to an md array, then resizing the partition and then resizing the filesystem (and removing a device is even worse). Snapshots are a similar deal - sure, LVM can let you snapshot your entire virtual block device, but your snapshots are block devices themselves which need to be explicitly mounted, while in btrfs/bcachefs a snapshot is just a directory, and can be isolated to a specific subvolume rather than the entire block device.

Data checksums are also substantially less useful when the filesystem can't address the underlying devices individually, because it makes repairing the data from a replica impossible. If you have a file on an md RAID1 device and one of the replicas has a bad block, you might be able to detect the bitrot by verifying the checksum, but you can't actually fix it, because even though there is a second copy of the data on another drive, mdadm simply exposes a simple block device and doesn't provide any way to read from "the other copy". mdraid can recover from total drive failure, but not data corruption.

[–] ReversalHatchery 5 points 1 month ago* (last edited 1 month ago) (1 children)

Honestly I'm fine with ZFS on larger scale, but on desktop I want a filesystem that can do compression (like NTFS on windows) and snapshots.

I have actually used compression a lot, and it spared me a lot of space. No, srorage is not cheap, or else I'm awaiting your shipment.
Other than that I'm doing differential backups on windows, and from time to time it's very useful that I can grab a file to which something just happened. Snapshots cost much less storage than complete copies, which I couldn't afford, but this way I have daily diffs for a few years back, and it only costs a TB or so.

[–] neutronst4r 3 points 1 month ago (1 children)

Sadly I have yet to see a truly compassionate FS 🥲

[–] ReversalHatchery 1 points 1 month ago

Yeah, same :D

It was a typo, I have meant compression. Specifically a per-file controlled compression, not per-directory or per-dataset.

[–] Damage@feddit.it 4 points 1 month ago (2 children)
[–] pimeys@lemmy.nauk.io 5 points 1 month ago (1 children)

One of the best filesystem codebases out there. Really a top notch file system if you don't need to resize it once it's created. It is a write through, not copy on write, so some features such as snapshots are not possible using XFS. If you don't care about features found in btrfs, zfs or bcachefs, and you don't need to resize the partition after creating it, XFS is a solid and very fast choice.

Ext4 codebase is known to be very complex and some people say even scary. It just works because everybody's using it and bugs have been fixed years ago.

[–] nous@programming.dev 2 points 1 month ago

Ext4 codebase is known to be very complex and some people say even scary. It just works because everybody’s using it and bugs have been fixed years ago.

I heard that ext4s best feature was its fsck utils being extremely robust and able to recover from a lot of problems. Which does not shine a great light on the filesystem itself :/ and probably a result of the complex codebase.

[–] possiblylinux127@lemmy.zip 1 points 1 month ago (1 children)

What's cool about bcache is that it can have fully tiered storage. It can move data from a hard drive to a SSD and vis versa. It isn't a cache like in ZFS as ZFS wipes the cache drive on mount and adding a cache doesn't increase capacity

[–] soundconjurer@mstdn.social 1 points 1 month ago* (last edited 1 month ago)

@possiblylinux127 @DaPorkchop_. ZFS has a persistent L2ARC cache now.