this post was submitted on 25 Apr 2025
50 points (98.1% liked)
Linux
7114 readers
712 users here now
A community for everything relating to the GNU/Linux operating system
Also check out:
Original icon base courtesy of [email protected] and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That's been the default for years
The big reason is that btrfs has more features like copy on write, snapshots, subvolumes and data validation.
It used to eat data but that's not been the case for a few years
Another great thing about BTRFS is that it can detect hardware problems sooner: if your BTRFS drive keeps losing data to corruption; that's because it has detected a corruption that other FS's would silently work with
Isn't that a RAID5/6 thing?
It used to eat data regardless even when it was supposedly stable
In newer kernels I believe raid5/6 are stable but the dangerousness thing is that it takes a huge amount of time to rebuild. I think this is true of raid10 as well.
I'm talking about the implementation of RAID5/6 for BTRFS specifically.
BTRFS documentation
Do you know if the documentation is outdated? Has this changed recently?