On Jan 28, 2013, at 4:23 PM, Wolfgang Denk <wd@xxxxxxx> wrote: > > Well, I did this - the repair worked without errors, but it left again > a huge mismatch_cnt; raid6check on this array has not found any > problems so far - even though I see mismatch_cnt = 362731480 Well, we don't know the nature of the bug. Also the method of testing can be confusing. If this is a bug, and you used the buggy version combination to do a repair, maybe it's seeing good parity as bad parity, and that's where the high mismatch count comes from. But then it replaces it with new parity, which could actually be bad, but either scrub or raid6check affected by the bug is seeing the bad parity as correct, hence no error. And my speculation is likely not helpful. I think more eyeballs need to be on this to try and get a reproducer, and find out what's going on. So you should probably post something on the Fedora devel list. If it's a bug, better to squash it sooner than later. If it's a false alarm, oh well not much harm done. Chris Murphy-- 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
