[danudey]

In 2019 I was setting up my new computer at my new job, and the Ubuntu installer had btrfs as an option. Figuring that it had been ages since the last time I'd heard about btrfs issues, I opted for that.

A week later, the power failed in the office, and my filesystem got corrupted. In the middle of repairing, the power dipped again, and my entire fs was unrecoverable after that. I managed to get the data off by booting off a separate drive and running a command to extract everything, but it would never mount no matter what I did.

I've never had an issue with ext4, xfs, or zfs no matter how much I've abused them over the past 10+ years, but if losing power twice can wipe out my filesystem then no thanks, I'm out.

(Plus: non-recursive snapshots? No thanks.)

[viraptor]

Are you sure you never had an issue, or did you just not notice? Ext4 and xfs can mangle your files and never let you know because they don't checksum. This comes up often in comparisons and I wish people paid attention to the difference.

[silisili]

Yeah...I used to live in an old neighborhood with above ground lines and huuuge trees. Every strong windblow would flip the power out for a second. Some days a few times a day, some days never.

EXT4 has never once failed me, and I personally battle tested it by working while losing power probably a total of 200 times. I probably should have bought a UPS come to think of it.

[Dylan16807]

Was it RAID5/6? If not that's worrying. I've had one BTRFS system eat itself to the point that it could only be mounted read-only, but no data loss.

[codys]

Not the OP, but I deployed btrfs on tens of embedded systems that had their power consistently cut on a daily basis. Ended up with unmountable filesystems repeatedly. Switched to ext4 and never had an unmountable filesystem again.

These were single disk systems, no raid at all.