imsm: FIX: Size is already set in metadata

In metadata size is set already during migration initialization.
There is no reason for second /the same/ calculation.

Signed-off-by: Adam Kwolek <adam.kwolek@intel.com>
Signed-off-by: NeilBrown <neilb@suse.de>

diff --git a/super-intel.c b/super-intel.c
index 4f92c01ca51689cba16c98ecb8087ebbea3c68cd..d049cb7728693ef0372c36acba418527a555df9b 100644 (file)
--- a/super-intel.c
+++ b/super-intel.c
@@ -5197,18 +5197,13 @@ static int imsm_set_array_state(struct active_array *a, int consistent)
                                        array_blocks = (array_blocks
                                                        >> SECT_PER_MB_SHIFT)
                                                << SECT_PER_MB_SHIFT;
-                                       dev->size_low = __cpu_to_le32(
-                                               (__u32) array_blocks);
-                                       dev->size_high = __cpu_to_le32(
-                                               (__u32) (array_blocks >> 32));
                                        a->info.custom_array_size = array_blocks;
                                        /* encourage manager to update array
                                         * size
                                         */
-                                       super->updates_pending++;
 
                                        a->check_reshape = 1;
-                               }
+}
                                /* finalize online capacity expansion/reshape */
                                for (mdi = a->info.devs; mdi; mdi = mdi->next)
                                        imsm_set_disk(a,