Xiao Ni <xni@xxxxxxxxxx> writes: > When reshaping a 3 drives raid5 to 4 drives raid5, there is a chance that > it can't start the reshape. If the disks are not enough to have spaces for > relocating the data_offset, it needs to call start_reshape and then run > mdadm --grow --continue by systemd. But mdadm --grow --continue fails > because it checkes that info->reshape_active is 0. > > The info->reshape_active is got from the superblock of underlying devices. > Function start_reshape write reshape to /sys/../sync_action. Before writing > latest superblock to underlying devices, mdadm --grow --continue is called. > There is a chance info->reshape_active is 0. We should wait for superblock > updating more time before calling Grow_continue. > > Signed-off-by: Xiao Ni <xni@xxxxxxxxxx> > --- > Grow.c | 67 ++++++++++++++++++++++++++++++++++++------------------------------ > 1 file changed, 37 insertions(+), 30 deletions(-) Applied! Thanks, Jes -- 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
