summaryrefslogtreecommitdiffstats
path: root/drivers/md
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-01-31 04:30:27 +0100
committerNeilBrown <neilb@suse.de>2011-01-31 04:30:27 +0100
commit7281f8129c362436237b82c8c026494dd36479dc (patch)
treec12196b42c807d4ee80d5f6e1657f31fa3ea4d7b /drivers/md
parentmd: Don't use remove_and_add_spares to remove failed devices from a read-only... (diff)
downloadlinux-7281f8129c362436237b82c8c026494dd36479dc.tar.xz
linux-7281f8129c362436237b82c8c026494dd36479dc.zip
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>
Diffstat (limited to 'drivers/md')
-rw-r--r--drivers/md/md.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/drivers/md/md.c b/drivers/md/md.c
index 5b93829f3d49..f2d5628d51cb 100644
--- a/drivers/md/md.c
+++ b/drivers/md/md.c
@@ -6984,9 +6984,6 @@ void md_do_sync(mddev_t *mddev)
} else if (test_bit(MD_RECOVERY_REQUESTED, &mddev->recovery))
mddev->resync_min = mddev->curr_resync_completed;
mddev->curr_resync = 0;
- if (!test_bit(MD_RECOVERY_INTR, &mddev->recovery))
- mddev->curr_resync_completed = 0;
- sysfs_notify(&mddev->kobj, NULL, "sync_completed");
wake_up(&resync_wait);
set_bit(MD_RECOVERY_DONE, &mddev->recovery);
md_wakeup_thread(mddev->thread);