summaryrefslogtreecommitdiffstats
path: root/super0.c
diff options
context:
space:
mode:
authorAdam Kwolek <adam.kwolek@intel.com>2011-10-05 04:30:50 +0200
committerNeilBrown <neilb@suse.de>2011-10-05 04:30:50 +0200
commit6e75048bc5121a3db33896b628683cdf7dc0d773 (patch)
tree1c2b9eb57b8b1bbfc7e30c6a382c4cc82d6ecdf6 /super0.c
parentrestore_backup() throws core dump (diff)
downloadmdadm-6e75048bc5121a3db33896b628683cdf7dc0d773.tar.xz
mdadm-6e75048bc5121a3db33896b628683cdf7dc0d773.zip
Add recovery blocked field to mdinfo
When container is assembled while reshape is active on one of its member whole container can be required to be blocked from monitoring. For such purpose field recovery blocked is added to mdinfo structure. When metadata handler finds active reshape in container it should set recovery_blocked field to disable whole container monitoring during reshape. For arrays that doesn't use containers, recovery_blocked field has the same value as reshape_active field e.g. super0/1. In fact,recovery is blocked during reshape for such arrays. For ddf, metadata handler doesn't set reshape_active field, so recovery_blocked is not set also. Signed-off-by: Adam Kwolek <adam.kwolek@intel.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'super0.c')
-rw-r--r--super0.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/super0.c b/super0.c
index f791e9d7..3061ecfe 100644
--- a/super0.c
+++ b/super0.c
@@ -387,6 +387,8 @@ static void getinfo_super0(struct supertype *st, struct mdinfo *info, char *map)
} else
info->reshape_active = 0;
+ info->recovery_blocked = info->reshape_active;
+
sprintf(info->name, "%d", sb->md_minor);
/* work_disks is calculated rather than read directly */
for (i=0; i < MD_SB_DISKS; i++)