Revision 60fc13702a1b35118c1548e9c257fa038cecb658 authored by NeilBrown on 22 December 2011, 22:57:19 UTC, committed by NeilBrown on 22 December 2011, 22:57:19 UTC
Before performing a recovery we try to remove any spares that might not be working, then add any that might have become relevant. Currently we abort on the first spare that cannot be added. This is a false optimisation. It is conceivable that - depending on rules in the personality - a subsequent spare might be accepted. Also the loop does other things like count the available spares and reset the 'recovery_offset' value. If we abort early these might not happen properly. So remove the early abort. In particular if you have an array what is undergoing recovery and which has extra spares, then the recovery may not restart after as reboot as the could of 'spares' might end up as zero. Reported-by: Anssi Hannula <anssi.hannula@iki.fi> Signed-off-by: NeilBrown <neilb@suse.de>
1 parent 30d7a48
| File | Mode | Size |
|---|---|---|
| hidraw | ||
| hw_breakpoint | ||
| kdb | ||
| kfifo | ||
| kobject | ||
| kprobes | ||
| trace_events | ||
| tracepoints | ||
| Kconfig | -rw-r--r-- | 1.7 KB |
| Makefile | -rw-r--r-- | 148 bytes |
Computing file changes ...
