summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-08-03 10:59:57 +1000
committerNeilBrown <neilb@suse.de>2009-08-03 10:59:57 +1000
commite516402c0d4fc02be4af9fa8c18954d4f9deb44e (patch)
tree8fa40d8f835d643ed903e1a89567a53256acc395 /drivers/md
parent70471dafe3390243c598a3165dfb86b8b8b3f4fe (diff)
downloadop-kernel-dev-e516402c0d4fc02be4af9fa8c18954d4f9deb44e.zip
op-kernel-dev-e516402c0d4fc02be4af9fa8c18954d4f9deb44e.tar.gz
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.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c
index 3937423..659151e 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);
OpenPOWER on IntegriCloud