summaryrefslogtreecommitdiffstats
path: root/super0.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2010-02-04 12:02:09 +1100
committerNeilBrown <neilb@suse.de>2010-02-04 12:02:09 +1100
commit921d9e164fd3f6203d1b0cf2424b793043afd001 (patch)
treead0fa1ec1343bd28676de6907177189ed14a748c /super0.c
parentcc86f89c855fcfe9820d0621ede1575adc317155 (diff)
downloadmdadm-921d9e164fd3f6203d1b0cf2424b793043afd001.tar.gz
mdadm-921d9e164fd3f6203d1b0cf2424b793043afd001.tar.xz
mdadm-921d9e164fd3f6203d1b0cf2424b793043afd001.zip
Assemble: fix --force assembly of v1.x arrays which are recovering.
1.x metadata allows a device to be a member of the array while it is still recoverying. So it is a working member, but is not completely in-sync. mdadm/assemble does not understand this distinction and assumes that a work member is fully in-sync for the purpose of determining if there are enough in-sync devices for the array to be functional. So collect the 'recovery_start' value from the metadata and use it in assemble when determining how useful a given device is. Reported-by: Mikael Abrahamsson <swmike@swm.pp.se> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'super0.c')
-rw-r--r--super0.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/super0.c b/super0.c
index 0485a3a..5c6b7d7 100644
--- a/super0.c
+++ b/super0.c
@@ -372,6 +372,7 @@ static void getinfo_super0(struct supertype *st, struct mdinfo *info)
uuid_from_super0(st, info->uuid);
+ info->recovery_start = MaxSector;
if (sb->minor_version > 90 && (sb->reshape_position+1) != 0) {
info->reshape_active = 1;
info->reshape_progress = sb->reshape_position;