On Friday March 18, [EMAIL PROTECTED] wrote:
>
> Is there perhaps some bug that denies a resync on a degraded
> RAID1 even if there is more than one mirror operational?
>
Yes :-(
The following patch might fix it...
I guess I should double check and submit something to Marcelo.
Thanks for reporting this.
NeilBrown
Signed-off-by: Neil Brown <[EMAIL PROTECTED]>
### Diffstat output
./drivers/md/raid1.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff ./drivers/md/raid1.c~current~ ./drivers/md/raid1.c
--- ./drivers/md/raid1.c~current~ 2004-08-16 10:17:11.000000000 +1000
+++ ./drivers/md/raid1.c 2005-03-22 09:47:11.000000000 +1100
@@ -1737,10 +1737,11 @@ static int raid1_run (mddev_t *mddev)
}
}
- if (!start_recovery && !(sb->state & (1 << MD_SB_CLEAN)) &&
+ if (!(sb->state & (1 << MD_SB_CLEAN)) &&
(conf->working_disks > 1)) {
const char * name = "raid1syncd";
+ start_recovery = 0;
conf->resync_thread = md_register_thread(raid1syncd, conf,name);
if (!conf->resync_thread) {
printk(THREAD_ERROR, mdidx(mddev));
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html