On Wednesday February 25, Paul.Clements@SteelEye.com wrote: > The attached patch makes sure that resync/recovery get aborted (and > status recorded correctly) when there are no spare drives left (due to > the failure of a spare during a resync). Previously, if a spare failed > during a resync, the resync would continue until completed (and would > appear to be successful). Hi, could you clarify exactly what the problem is. As far as I can see (without looking very deeply) the only problem is that the resync process continues on when there is no point doing so, thus wasting time. At the end of the process, any devices that failed should still be marked failed and so the array will be insync, but might be degraded - but there is no risk to data. Am I missing something? (I"m not saying I don't like the patch - it looks like a good idea - I just want to be sure I understand it). NeilBrown - To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
