summaryrefslogtreecommitdiffstats
path: root/kernel
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2007-10-16 23:30:55 -0700
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-10-17 08:43:03 -0700
commitcf7a44168d743ca97863b7f34ed42a45fd7b5ab0 (patch)
tree884f5094a46be4da9f30292c9a5a417f100d5d5f /kernel
parentd7f3d291a0e1330f341fdf1128b2d12fff7932ee (diff)
downloadop-kernel-dev-cf7a44168d743ca97863b7f34ed42a45fd7b5ab0.zip
op-kernel-dev-cf7a44168d743ca97863b7f34ed42a45fd7b5ab0.tar.gz
md: make sure read errors are auto-corrected during a 'check' resync in raid1
Whenever a read error is found, we should attempt to overwrite with correct data to 'fix' it. However when do a 'check' pass (which compares data blocks that are successfully read, but doesn't normally overwrite) we don't do that. We should. Signed-off-by: Neil Brown <neilb@suse.de> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'kernel')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud