←back to thread

144 points ksec | 1 comments | | HN request time: 0.223s | source
Show context
zahlman ◴[] No.44468213[source]
Does the filesystem actually need to be part of the kernel project to work? I can see where you'd need that for the root filesystem, but even then, couldn't one migrate an existing installation to a new partition with a different filesystem?
replies(4): >>44468621 #>>44468749 #>>44470079 #>>44471033 #
teekert ◴[] No.44468621[source]
We ZFS for that. What we want is something in kernel, ready to go, 100% supported on root ok any Linux system with no license ambiguity. We want to replace ext4. Maybe btrfs can do it. I hear it has outgrown its rocky puberty.
replies(1): >>44468869 #
alphazard ◴[] No.44468869[source]
Bcachefs and Btrfs are not really competing with Ext4. There are basically 2 filesystem niches.

First niche is the full featured CoW filesystem; it has snapshots, detects and repairs corruption, transparent compression, all that good stuff.

The other niche is being an allocator of sectors. There's one storage device, divide it up amongst all these processes asking for storage. That's Ext4: an allocator of disk sectors, dressed up in a filesystem API. When you are running databases or VMs, all you want is an allocator of sectors. You don't want lots of stuff getting in the way of your writes. You don't want checksumming, you don't want your writes going to a new place every time. You just want write access to part of the disk.

replies(4): >>44470271 #>>44470974 #>>44471079 #>>44474304 #
1. samus ◴[] No.44471079[source]
At the same time, many VM and containerization solutions build these features themselves. It seems attractive to reuse the heavily optimized machinery that a COW filesystem offers. And indeed at least Docker can use Btrfs snapshots to create images. It has been a while since I looked into it though; no clue how mature and performant it is nowadays.

https://docs.docker.com/engine/storage/drivers/btrfs-driver/