summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Lyakas <alex.bolshoy@gmail.com>2012-05-13 10:10:43 +0300
committerNeilBrown <neilb@suse.de>2012-05-15 14:20:42 +1000
commit135a31f5ed39dfc5d0288fac7ae8af8f5b2ae233 (patch)
treede2e244d88848df4fdeb4ee79fe3f48678555381
parentc456301a05dcbb3267ef13cd83e10c6867ea34ea (diff)
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 <neilb@suse.de>
-rw-r--r--Assemble.c1
1 files changed, 1 insertions, 0 deletions
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;