When a raid personality reports an error we should make sure
that recovery is aborted.
Normally it would be anyway, as an IO error will cause
md_error to be called which aborts recovery.
However, in raid5, if two drives fail before recovery starts, then no
error will actually happen during recovery, but the raid5 module
will report each resync request as failing. We really shouldn't
ignore this...
----------- Diffstat output ------------
./drivers/md/md.c | 4 ++++
1 files changed, 4 insertions(+)
--- ./drivers/md/md.c 2002/05/15 05:36:13 1.1
+++ ./drivers/md/md.c 2002/05/15 05:38:05 1.2
@@ -3332,6 +3332,10 @@
wake_up(&mddev->recovery_wait);
if (!ok) {
// stop recovery, signal do_sync ....
+ if (mddev->pers->stop_resync)
+ mddev->pers->stop_resync(mddev);
+ if (mddev->recovery_running)
+ md_interrupt_thread(md_recovery_thread);
}
}
-
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
