diff options
author | NeilBrown <neilb@suse.de> | 2006-01-06 00:20:29 -0800 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-01-06 08:34:05 -0800 |
commit | 0eb3ff12aa8a12538ef681dc83f4361636a0699f (patch) | |
tree | e5d4b8353362cefd096a4b1ee1a8f473c01169b6 /kernel | |
parent | 4443ae10ca15d07922ceda622f03db8865fa3d13 (diff) | |
download | kernel_samsung_aries-0eb3ff12aa8a12538ef681dc83f4361636a0699f.zip kernel_samsung_aries-0eb3ff12aa8a12538ef681dc83f4361636a0699f.tar.gz kernel_samsung_aries-0eb3ff12aa8a12538ef681dc83f4361636a0699f.tar.bz2 |
[PATCH] md: raid10 read-error handling - resync and read-only
Add in correct read-error handling for resync and read-only situations.
When read-only, we don't over-write, so we need to mark the failed drive in
the r10_bio so we don't re-try it. During resync, we always read all blocks,
so if there is a read error, we simply over-write it with the good block that
we found (assuming we found one).
Note that the recovery case still isn't handled in an interesting way. There
is nothing useful to do for the 2-copies case. If there are 3 or more copies,
then we could try reading from one of the non-missing copies, but this is a
bit complicated and very rarely would be used, so I'm leaving it for now.
Signed-off-by: Neil Brown <neilb@suse.de>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions