diff options
author | NeilBrown <neilb@suse.de> | 2009-08-03 02:59:57 +0200 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2009-08-03 02:59:57 +0200 |
commit | e516402c0d4fc02be4af9fa8c18954d4f9deb44e (patch) | |
tree | 8fa40d8f835d643ed903e1a89567a53256acc395 /drivers/md | |
parent | md: Handle growth of v1.x metadata correctly. (diff) | |
download | linux-e516402c0d4fc02be4af9fa8c18954d4f9deb44e.tar.xz linux-e516402c0d4fc02be4af9fa8c18954d4f9deb44e.zip |
md/raid5: set reshape_position correctly when reshape starts.
As the internal reshape_progress counter is the main driver
for reshape, the fact that reshape_position sometimes starts with the
wrong value has minimal effect. It is visible in sysfs and that
is all.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md')
-rw-r--r-- | drivers/md/raid5.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 39374230a463..659151e5eda4 100644 --- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -5000,7 +5000,7 @@ static int raid5_start_reshape(mddev_t *mddev) spin_unlock_irqrestore(&conf->device_lock, flags); } mddev->raid_disks = conf->raid_disks; - mddev->reshape_position = 0; + mddev->reshape_position = conf->reshape_progress; set_bit(MD_CHANGE_DEVS, &mddev->flags); clear_bit(MD_RECOVERY_SYNC, &mddev->recovery); |