| commit | 7281f8129c362436237b82c8c026494dd36479dc | |
| author | NeilBrown <neilb@suse.de> | |
| Mon, 31 Jan 2011 03:30:27 +0000 (31 14:30 +1100) | ||
| committer | NeilBrown <neilb@suse.de> | |
| Mon, 31 Jan 2011 03:30:27 +0000 (31 14:30 +1100) | ||
| tree | c12196b42c807d4ee80d5f6e1657f31fa3ea4d7b | treesnapshot (tar.gz zip) |
| parent | a8c42c7f476b5bb39bb3a5b32d5473b9a46cadb9 | commitdiff |
md: don't clear curr_resync_completed at end of resync.
There is no need to set this to zero at this point. It will be
set to zero by remove_and_add_spares or at the start of
md_do_sync at the latest.
And setting it to zero before MD_RECOVERY_RUNNING is cleared can
make a 'zero' appear briefly in the 'sync_completed' sysfs attribute
just as resync is finishing.
So simply remove this setting to zero.
Signed-off-by: NeilBrown <neilb@suse.de>
There is no need to set this to zero at this point. It will be
set to zero by remove_and_add_spares or at the start of
md_do_sync at the latest.
And setting it to zero before MD_RECOVERY_RUNNING is cleared can
make a 'zero' appear briefly in the 'sync_completed' sysfs attribute
just as resync is finishing.
So simply remove this setting to zero.
Signed-off-by: NeilBrown <neilb@suse.de>
| drivers/md/md.c | diffblobblamehistory |