12 ms·

Don't use RAID5/6 in production. This is well-documented , and the remaining issue (the write hole) is being worked on. As with any software, don't use features

Don't use RAID5/6 in production. This is well-documented , and the remaining issue (the write hole) is being worked on. As with any software, don't use features not marked stable in production. As for the write-only bug, 1) that only affects 2-disk RAID1 setups where people insist on cowboying around with their degraded arrays, and 2) doesn't result in data loss, merely an additional copy step to restore the array. Don't run your arrays in a degraded state, please. As I wrote, SUSE considers Btrfs stable for production use, and they're the premier enterprise distro in Europe.

throw0101a 6y ago
> Don't run your arrays in a degraded state, please. That's easy to say, but if you get a bad disk in a mirror on your boot drives, and for some reason your system restarts during this time period, you boot up into read-only mode--which kind of keeps your server down and kills service availability. I don't run Btrfs, and so heard about this scenario from Jim Salter (the author of the linked Ars article) in his podcast: * https://2.5admins.com/2-5-admins-03/ https://2.5admins.com/2-5-admins-03/
oarsinsync 6y ago
> 2-disk RAID1 setups where people insist on cowboying around with their degraded arrays RAID1 is not a backup. Apparently under BTRFS, using RAID1 for HA isn’t acceptable either. What’s the point of a RAID1 array if you can’t use it degraded? Might as well just go RAID0 too then (you have backups anyway, right?)