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, Informative) by Anonymous Coward on Monday August 08 2016, @07:33AM
Morons.
In my experience, the primary use of backups is not hardware faults (including lightning-induced hardware faults), but human or software error overwriting or deleting stuff.
In this situation, RAID will ensure that the mistake is propagated to every drive within milliseconds.
Snapshots can remedy the human factor somewhat (as long as the person making the mistake doesn't have root access), but it doesn't protect against software problems (including controller and file system drivers).