As a Linux noob I first thought you were just facerolling on your keyboard. But then I read it as b-cache-fs. It’s a new file system, I take it?
Exactly! It is a new Btrfs competitor and OpenZFS alternative that is built upon the bcache codebase.
As someone else said, it’s similar to btrfs. bcachefs has a lot of functional overlap with btrfs, which is great. There have also been a few benchmarks showing that bcachesfs is faster for some situations (cold-cache warming, IIRC). One of the big advantages over btrfs is that bcachefs’s RAID is more robust - several of btrfs’s RAID levels have been marked as experimental and prone to data loss, for years. There’s been improvement in btrfs RAID lately; the skeptic in me believes this is directly a result of pressure from bcachefs, which is in a position to become a favored fs in Linux.
A lot of the time it obviously takes a little while for userland tools to catch up and for distros to include both the new kernel and userland tools for it into their latest versions but once that is done average users certainly do notice differences. Literally all the features that are talked about a lot like BPF or io_uring or all the features that make containers possible were introduced in a kernel release at some point.
Second person excited for bcachefs, I’m planning on swapping over as soon as it supports scrubbing.
I really hope it would be a working one, not like xfs where your files may just disappear with no trace (never on Irix, never on any other fs) or like btrfs which may just suddenly go read only and be dead on reboot with no fsck and all data unreachable.
How hard is it to get the basics right? Doesn’t matter how much rice there is if it keeps blowing up.
