> Btrfs is NOT constantly eating people data

Tell it to my data then. I was 100% invested in Btrfs before 2017, the year where I lost a whole filesystem due to some random metadata corruption. I then started to move all of my storage to ZFS, which has never ever lost me a single byte of data yet despite the fact it's out of tree and stuff. My last Btrfs filesystem died randomly a few days ago (it was a disk in cold storage, once again random metadata corruption, disk is 100% healthy). I do not trust Btrfs in any shape and form nowadays. I also vastly prefer ZFS tooling but that's irrelevant to the argument here. The point is that I've never had nothing but pain from btrfs in more than a decade

> Btrfs is NOT constantly eating people data. You have nothing to back this statement.

Constantly may be a strong word, but there is a long line of people sharing tales of woe. It's good that it works for you, but that's not a universal experience.

> It's widely used and the default filesystem of several distributions.

As a former user, that's horrifying.

> Most of the problems are like for the other filesystem: caused by the hardware.

The whole point of btrfs over (say) ext4 is that it's supposed to hold up when things don't work.

I think any discussion of btrfs needs to acknowledge that raid5/6 support was promised in the early years, shipped in the kernel in 2013 and, until 2021's btrfs-progs 5.11 release, did not warn users that they risked data loss when creating volumes.

For near a decade btrfs raid5/6 was "unsafe at any speed" and many people lost data to it, including myself.

btrfs has eaten my data, which was probably my bad for trying out a newly stable filesystem around 15 years ago. there are plenty of bug reports of btrfs eating other people's data in the years since.

It's probably mostly stable now, but it's silly to act like it's a paragon of stability in the kernel.

I would love to use xfs on my NAS setup but no checksums is a deal breaker. Checksums have saved me multiple times where I've been able to either repair files with parity or restore from backups.

Without checksums I would have overwritten my backup data and lost a ton of files because the drives were reported that everything was OK for months while writing corrupt files.

Thin provisioning with lvm is afaik problematic, because the file systems aren't aware of it and if you run out of space you're screwed