Fix some issues with setting 'new' state of a reshape

- when reshaping a container, ->reshape_active is already set
  even though it isn't really active yet, so we need to set
  the new geometry even when reshape_active is set.  This is safe.

- When restarting a reshape, make sure the reshape_position is set
  appropriately when external metadata is used.

Signed-off-by: NeilBrown <neilb@suse.de>

1 files changed, 9 insertions, 0 deletions

diff --git a/sysfs.c b/sysfs.c
index a9ece82b..f0773d47 100644
--- a/sysfs.c
+++ b/sysfs.c
@@ -569,6 +569,15 @@ int sysfs_set_array(struct mdinfo *info, int vers)
 
 	if (info->array.level > 0)
 		rv |= sysfs_set_num(info, NULL, "resync_start", info->resync_start);
+
+	if (info->reshape_active) {
+		rv |= sysfs_set_num(info, NULL, "reshape_position",
+				    info->reshape_progress);
+		rv |= sysfs_set_num(info, NULL, "chunk_size", info->new_chunk);
+		/* Don't set layout or raid_disks here as they require some
+		 * analysis and are set by reshape_array 
+		 */
+	}
 	return rv;
 }