From: Alexander Lyakas Date: Sun, 13 May 2012 07:10:43 +0000 (+0300) Subject: Don't consider disks with a valid recovery offset as candidates for bumping up event... X-Git-Tag: mdadm-3.2.5~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=135a31f5ed39dfc5d0288fac7ae8af8f5b2ae233;p=thirdparty%2Fmdadm.git Don't consider disks with a valid recovery offset as candidates for bumping up event count When we are looking for a candidate disk to bump up the event count, we consider only disks that have recovery_start==MaxSector. However, after we find one such disk, we agree to accept more disks having same event count, regardless of their recovery_start. Be consistent and don't accept disks with a valid recovery_start at all. Signed-off-by: NeilBrown --- diff --git a/Assemble.c b/Assemble.c index 080993df..227d66fc 100644 --- a/Assemble.c +++ b/Assemble.c @@ -1069,6 +1069,7 @@ int Assemble(struct supertype *st, char *mddev, int j = best[i]; if (j >= 0 && !devices[j].uptodate && + devices[j].i.recovery_start == MaxSector && devices[j].i.events == current_events) { chosen_drive = j; goto add_another;