md/raid5: use bad-block log to improve handling of uncorrectable read errors.

Browse source

If we get an uncorrectable read error - record a bad block rather than
failing the device.
And if these errors (which may be due to known bad blocks) cause
recovery to be impossible, record a bad block on the recovering
devices, or abort the recovery.

As we might abort a recovery without failing a device we need to teach
RAID5 about recovery_disabled handling.

Signed-off-by: NeilBrown <neilb@suse.de>

...

This commit is contained in:

NeilBrown 2011-07-28 11:39:22 +10:00

parent 31c176ecdf

commit 7f0da59bdc

2 changed files with 53 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

59

drivers/md/raid5.c

View file

2

drivers/md/raid5.h

View file