On Jan 31, 2013, at 11:36 AM, Wolfgang Denk <wd@xxxxxxx> wrote: > I cannot test the exact old kernel I was running before any more; > Fedora has released an update in the meantime, and they do not keep > older updates around They are in koji. > When using the (really old) kernel > from the installation media, I see the same behaviour as with current > mainline: I have to run a "repair", and then the array is, and > remains, clean. > > With the current Fedora kernel, the first check will report errors > which do not go away permanently, not even with a "repair". This is 3.7.4-204? Hypothetically this should be reproducible by anyone using that kernel, by creating a new raid6, running repair, and then running check and confirming thee mismatch count is non-zero. > > I did this, actually in parallel with reporting the issues here: > https://bugzilla.redhat.com/show_bug.cgi?id=904831 I defer to others but I'm not sure if the component is mdadm or if it's kernel, in this case. You've only changed kernels from 3.7.4-204 to 3.8-rc5, not mdadm. > I think the relevant Fedora people are on Cc:, but there was zero > response so far; seems potential data loss is of no concern to the > Fedora project :-( It's not atypical for there to be delays in responding to such things when it's not widespread, and as yet no one else has reproduced it even on this list. So we need reproducers, and they need to comment on the bug. Also a step by step to reproduce the bug is important, to help get people to try to reproduce it. 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
