On Thursday November 15, nixon@xxxxxxxxxx wrote: > Hi, > > I have been looking a bit at the check/repair functionality in the > raid6 personality. > > It seems that if an inconsistent stripe is found during repair, md > does not try to determine which block is corrupt (using e.g. the > method in section 4 of HPA's raid6 paper), but just recomputes the > parity blocks - i.e. the same way as inconsistent raid5 stripes are > handled. > > Correct? Correct! The mostly likely cause of parity being incorrect is if a write to data + P + Q was interrupted when one or two of those had been written, but the other had not. No matter which was or was not written, correctly P and Q will produce a 'correct' result, and it is simple. I really don't see any justification for being more clever. NeilBrown - 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
