The nice feller over at phoronix brings us this handy to have bit of info:
It turns out the RAID5 and RAID6 code for the Btrfs file-system's built-in RAID support is faulty and users should not be making use of it if you care about your data.
There has been this mailing list thread since the end of July about Btrfs scrub recalculating the wrong parity in RAID5. The wrong parity and unrecoverable errors has been confirmed by multiple parties. The Btrfs RAID 5/6 code has been called as much as fatally flawed -- "more or less fatally flawed, and a full scrap and rewrite to an entirely different raid56 mode on-disk format may be necessary to fix it. And what's even clearer is that people /really/ shouldn't be using raid56 mode for anything but testing with throw-away data, at this point. Anything else is simply irresponsible."
Just as well I haven't gotten around to trying it then.
(Score: 2, Insightful) by Anonymous Coward on Sunday August 07 2016, @03:06PM
Yes, RAID is not a replacement for backups. Both strategies should be used. I don't see how that's relevant.
Only a fool would use btrfs for production. Has btrfs ever had a stable release?
(Score: 2) by VLM on Sunday August 07 2016, @04:48PM
Has btrfs ever had a stable release?
Yeah, it shipped under the code name "ZFS on FreeBSD" back in '07
Oh Snap that was brutal. Someday though BTRFS in like 2027 might catch up to ZFS from 2007, well, someday. Maybe.
Seriously though, systemd, best thing ever, without that I wouldn't be using freebsd and discovering zfs and pf and stuff.
(Score: 1, Touché) by Anonymous Coward on Monday August 08 2016, @06:47AM
Only a fool would use btrfs for production. Has btrfs ever had a stable release?
Maybe somehow these bunch have a stable btrfs release: https://www.synology.com/en-global/dsm/Btrfs [synology.com]
:p