summaryrefslogtreecommitdiffstats
path: root/super-ddf.c
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-03-10 16:28:22 +1100
committerNeilBrown <neilb@suse.de>2009-03-10 16:28:22 +1100
commit661dce36178960a20a5bcbb3bbf92e721df1bec0 (patch)
tree84bc5f3fa9c8e482527b5fae9b9f4f8ac463dd60 /super-ddf.c
parentbc17324f5e0fd1631bfd9a8d749a34a94da4e621 (diff)
downloadmdadm-661dce36178960a20a5bcbb3bbf92e721df1bec0.tar.gz
mdadm-661dce36178960a20a5bcbb3bbf92e721df1bec0.tar.xz
mdadm-661dce36178960a20a5bcbb3bbf92e721df1bec0.zip
mdmon: allow incremental assembly of containers.
If mdmon sees a device added to a container, it should assume it is a new spare. It could be a part of the array that just hadn't been assembled yet. So check first. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'super-ddf.c')
-rw-r--r--super-ddf.c1
1 files changed, 1 insertions, 0 deletions
diff --git a/super-ddf.c b/super-ddf.c
index 965b8e2..6455dee 100644
--- a/super-ddf.c
+++ b/super-ddf.c
@@ -1335,6 +1335,7 @@ static void getinfo_super_ddf(struct supertype *st, struct mdinfo *info)
info->component_size = ddf->dlist->size - info->data_offset;
} else {
info->disk.number = -1;
+ info->disk.raid_disk = -1;
// info->disk.raid_disk = find refnum in the table and use index;
}
info->disk.state = (1 << MD_DISK_SYNC);