On Thu, Jan 31, 2013 at 10:14:35AM -0700, Chris Murphy wrote: > > On Jan 31, 2013, at 5:12 AM, Wolfgang Denk <wd@xxxxxxx> 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? Hi Chris, the code base is different, namely raid6check uses plain C, with no optimizations (that's why is so sloooow), while the kernel code has different paths, depending on which optimization is available and best. The algorithm should be the same. Nevertheless, the tests I run, intentionally and unintentionally, on raid6check were always consistent, so this surprise me. > > 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. I fully agree with this, what was seen there is for sure not normal. bye, -- piergiorgio -- 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
