Graham Fleming posted on Sun, 19 Jan 2014 16:53:13 -0800 as excerpted: > From the wiki, I see that scrubbing is not supported on a RAID 5 volume. > > Can I still run the scrub routing (maybe read-only?) to check for any > issues. I understand at this point running 3.12 kernel there are no > routines to fix parity issues with RAID 5 while scrubbing but just want > to know if I'm either a) not causing any harm by running the scrub on a > RAID 5 volume and b) it's actually goin to provide me with useful > feedback (ie file X is damaged).
This isn't a direct answer to your question, but answers a somewhat more basic question... Btrfs raid5/6 isn't ready for use in a live-environment yet, period, only for testing where the reliability of the data beyond the test doesn't matter. It works as long as everything works normally, writing out the parity blocks as well as the data, but besides scrub not yet being implemented, neither is recovery from loss of device, or from out-of-sync- state power-off. Since the whole /point/ of raid5/6 is recovery from device-loss, without that it's simply a less efficient raid0, which accepts the risk of fully data loss if a device is lost in ordered to gain the higher thruput of N- way data striping. So in practice at this point, if you're willing to accept loss of all data and want the higher thruput, you'd use raid0 or perhaps single mode instead, or if not, you'd use raid1 or raid10 mode. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
