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@xxxxxxxxx> --- super-intel.c | 5 +---- 1 files changed, 1 insertions(+), 4 deletions(-) diff --git a/super-intel.c b/super-intel.c index 42f7065..62b13b0 100644 --- a/super-intel.c +++ b/super-intel.c @@ -5185,15 +5185,12 @@ static int imsm_set_array_state(struct active_array *a, int consistent) /* round array size down to closest MB */ 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/2; a->check_reshape = 1; /* encourage manager to update * array size */ - super->updates_pending++; imsm_progress_container_reshape(super); - } + } } } -- To unsubscribe from this list: send the line "unsubscribe linux-raid" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
