On Jan 28, 2013, at 4:03 PM, Wolfgang Denk <wd@xxxxxxx> wrote: > Dear Chris, > > In message <1CEFA702-4512-40C1-ABE4-0FF7F42D9F44@xxxxxxxxxxxxxxxxx> you wrote: >> >> Actually it also needs to be reproduced as well. Wolfgang, the >> arrays were created/running under what version of mdadm and kernel >> the last time you did a check and there were no problems? > > No. The arrays were created before the update, and were running fine > by then. The most recent of them was created under Fedora 17 - the > other two are much older; it would take a bit of effort to find out > when I created these, and with which exact versions. > > The last time bbefore the update to Fedora 18, all systems were > running Fedora 17 (with almost all updates installed), and there were > no problems. Yes but what kernel version and mdadm? Right now 3.7.3-104 is stable kernel for Fedora 17, and 3.2.6-8 for mdadm for Fedora 17. So saying Fedora 17 tells not very much. > >> And now you're on Fedora 18, but the problem appeared with what >> version of mdadm and kernel? > > The problem showed up during the first check after updating to Fedora > 18. This is with: > > kernel-3.7.4-204.fc18.x86_64 > mdadm-3.2.6-12.fc18.x86_64 OK and the versions before that, that you know the problem was not occurring? 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
