| Date | Sun, 06 Dec 2009 15:59:46 -0800 | From | Greg KH <> | Subject | [010/119] md/raid5: make sure curr_sync_completes is uptodate when reshape starts |
| |
2.6.31-stable review patch. If anyone has any objections, please let us know.
------------------ From: NeilBrown <neilb@suse.de>
commit 8dee7211467a56b7eb4e4359efb0aa4a72e1b6f3 upstream.
This value is visible through sysfs and is used by mdadm when it manages a reshape (backing up data that is about to be rearranged). So it is important that it is always correct. Current it does not get updated properly when a reshape starts which can cause problems when assembling an array that is in the middle of being reshaped.
This is suitable for 2.6.31.y stable kernels.
Signed-off-by: NeilBrown <neilb@suse.de> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
--- drivers/md/raid5.c | 2 ++ 1 file changed, 2 insertions(+)
--- a/drivers/md/raid5.c +++ b/drivers/md/raid5.c @@ -3790,6 +3790,8 @@ static sector_t reshape_request(mddev_t sector_nr = conf->reshape_progress; sector_div(sector_nr, new_data_disks); if (sector_nr) { + mddev->curr_resync_completed = sector_nr; + sysfs_notify(&mddev->kobj, NULL, "sync_completed"); *skipped = 1; return sector_nr; }
|