Make sure reshape_active is cleared by getinfo_super

There were cases where --detail would report phantom reshapes.

Signed-off-by: NeilBrown <neilb@suse.de>
This commit is contained in:
NeilBrown 2010-03-09 16:15:29 +11:00
parent ecdbb368f8
commit 624c5ad4cb
2 changed files with 2 additions and 0 deletions

View File

@ -1434,6 +1434,7 @@ static void getinfo_super_ddf_bvd(struct supertype *st, struct mdinfo *info)
info->recovery_start = MaxSector;
info->resync_start = 0;
info->reshape_active = 0;
if (!(ddf->virt->entries[info->container_member].state
& DDF_state_inconsistent) &&
(ddf->virt->entries[info->container_member].init_state

View File

@ -1453,6 +1453,7 @@ static void getinfo_super_imsm_volume(struct supertype *st, struct mdinfo *info)
info->component_size = __le32_to_cpu(map->blocks_per_member);
memset(info->uuid, 0, sizeof(info->uuid));
info->recovery_start = MaxSector;
info->reshape_active = 0;
if (map->map_state == IMSM_T_STATE_UNINITIALIZED || dev->vol.dirty) {
info->resync_start = 0;