On 03/15/2011 02:13 PM, Robin Hill wrote: > On Tue Mar 15, 2011 at 01:43:01PM +0000, Bas van Schaik wrote >> My other question is still standing: >>> Furthermore, theoretically it should be possible to indicate which >>> device in the RAID-6 array contains the inconsistent data, or am I >>> mistaking? If so, that would certainly be a nice feature to see >>> implemented, as it would help diagnosing problems. >> Am I indeed correct in thinking this? > I'm not sure. If it's a single data block that's failed then you should > be able to, for each disk, re-generate the data using the other disks > and the P parity, then validate against the Q parity (if it matches then > that disk is the incorrect one). You should also be able to detect > errors in either the P or Q parity (if one is valid for the data and the > other isn't). If there's multiple disks which are incorrect then I > don't think there's any way you can tell which (or even avoid having one > of the correct disks flagged as incorrect). Indeed, that is what I was thinking. As I've just discovered some new block mismatches (that's 2 weeks after the last repair!) on my 8x2TB RAID6 array, it would be really nice to see this feature implemented... I would be happy to contribute, but I am not very experienced in hacking kernel C. Any tips, tricks and/or suggestions anyone? Cheers, Bas -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
