2006/6/30, Ákos Maróy <darkeye@xxxxxxxxx>:
Francois, Thank you for the very swift response. > First, what is your mdadm version ? # mdadm --version mdadm - v1.12.0 - 14 June 2005
Rather old, version, isn't it ? The freshest meat is 2.5.2, and can be grabbed here : http://www.cse.unsw.edu.au/~neilb/source/mdadm/ It's quite strange that you have such an old mdadm with a 2.6.16 kernel. That could be a good idea to upgrade...
what I see is that /dev/sdb1 is signaled as faulty (though it was known to be not fault before the power failure), and that the whole array is dirty because of the power failure - thus it can't resync.
Yep, this looks like it. The events difference is quite big : 0.2701790 vs. 0.2607131... Could it be that the sdb1 was marked faulty a couple of seconds before the power failure ?
but even if I hot-add /dev/sdb1 after starting the array, it will say that it's resyncing, but actually nothing will happen (no disk activity according to vmstat, no CPU load, etc.)
That's strange. Once again, maybe upgrading your mdadm. If it does not make it, I guess you'll have to re-constuct your array. That does not necessarily mean you'll loose data, just playing with -C and miscelaneous stuff, but I'm not good at that games... Neil is, definitly. Good luck. - 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
