summaryrefslogtreecommitdiffstats
path: root/Assemble.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2008-11-27 15:46:51 +1100
committerNeilBrown <neilb@suse.de>2008-11-27 15:46:51 +1100
commitd555f101466ab9ad72399c8de92713230e2c9c77 (patch)
treebc05d72459cd73f82109bf832bd8c1cf2bb56cf8 /Assemble.c
parent35e3446bfeaa4f2a04517ac115710061b704d3a5 (diff)
downloadmdadm-d555f101466ab9ad72399c8de92713230e2c9c77.tar.gz
mdadm-d555f101466ab9ad72399c8de92713230e2c9c77.tar.xz
mdadm-d555f101466ab9ad72399c8de92713230e2c9c77.zip
Assemble: allow --force to work even when event counts are 0.
If any superblocks in a confused array had an event count of 0, "mdadm -Af" would not update the event counts to assemble the array. I don't remember why that text is there, and it has caused at least one situation to be difficult to recover from. So remove the test. --force means --force! Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'Assemble.c')
-rw-r--r--Assemble.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/Assemble.c b/Assemble.c
index 79f0912..1d37870 100644
--- a/Assemble.c
+++ b/Assemble.c
@@ -632,7 +632,6 @@ int Assemble(struct supertype *st, char *mddev, int mdfd,
int j = best[i];
if (j>=0 &&
!devices[j].uptodate &&
- devices[j].i.events > 0 &&
(chosen_drive < 0 ||
devices[j].i.events
> devices[chosen_drive].i.events))
@@ -690,7 +689,6 @@ int Assemble(struct supertype *st, char *mddev, int mdfd,
int j = best[i];
if (j >= 0 &&
!devices[j].uptodate &&
- devices[j].i.events > 0 &&
devices[j].i.events == current_events) {
chosen_drive = j;
goto add_another;