I’ve only recently been made aware of btrfs’ tendency to completely fuck data at failure states.
I’ve been using that filesystem on fedora for maybe two years now without issue, though I suppose I don’t regularly find myself hitting the issues required to cause these problems.
It has now been nearly eight years since the “experimental” tag was removed, but many of btrfs’ age-old problems remain unaddressed and effectively unchanged. So, we’ll repeat this once more: as a single-disk filesystem, btrfs has been stable and for the most part performant for years. But the deeper you get into the new features btrfs offers, the shakier the ground you walk on—that’s what we’re focusing on today.
So if you’re just using it for your PC hard drive you’re probably fine. The problem is that BTRFS is intended to provide similar features to RAID and ZFS, but that’s where it starts failing.
I’ve only recently been made aware of btrfs’ tendency to completely fuck data at failure states.
I’ve been using that filesystem on fedora for maybe two years now without issue, though I suppose I don’t regularly find myself hitting the issues required to cause these problems.
Well yeah, like the article I linked says:
So if you’re just using it for your PC hard drive you’re probably fine. The problem is that BTRFS is intended to provide similar features to RAID and ZFS, but that’s where it starts failing.