Patrik Jonsson wrote: > Michael Tokarev wrote: [] >> But in any case, md should not stall - be it during reconstruction >> or not. For this, I can't comment - to me it smells like a bug >> somewhere (md layer? error handling in driver? something else?) >> which should be found and fixed. And for this, some more details >> are needed I guess -- kernel version is a start. > > Really? It's my understanding that if md finds an unreadable block > during raid5 reconstruction, it has no option but to fail since the > information can't be reconstructed. When this happened to me, I had to Yes indeed, it should fail, but not stuck as Daniel reported. Ie, it should either complete the work or fail, but not sleep somewhere in between. [] > This is why it's important to run a weekly check so md can repair blocks > *before* a drive fails. *nod*. /mjt - 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
