On Jan 31, 2013, at 5:12 AM, Wolfgang Denk [off-list ref] wrote:

After running a "repair" on the array, both "check" and "raid6test"
would not report any further issues.

Yes but this would be consistent with a derivative parity, written to disk and then checked against an algorithm that expects derivative parity. What happens if you go back to the old kernel before all the problems were happening and you do a check? What happens if you go back to a Fedora kernel you know exhibited the problem and you do a check?

Question for Piergiorgio is if check and raid6test use the same, or independent, code for checking parity?

I'll continue to watch this for a while, but I think I will not
"update" to a Fedora kernel for some time...

I think a bug needs to be filed with the information you have thus far.


Chris Murphy