summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2012-04-24 10:23:14 +1000
committerNeilBrown <neilb@suse.de>2012-04-24 10:23:14 +1000
commited209584c38fb74b7eecc03e5b1bfe674e591bd8 (patch)
treea232bb4fbf3a2e143ad57dfa3acad92418c5b12c /scripts
parenta9ad8526bb1af0741a5c0e01155dac08e7bdde60 (diff)
downloadop-kernel-dev-ed209584c38fb74b7eecc03e5b1bfe674e591bd8.zip
op-kernel-dev-ed209584c38fb74b7eecc03e5b1bfe674e591bd8.tar.gz
md: don't call ->add_disk unless there is good reason.
Commit 7bfec5f35c68121e7b18 md/raid5: If there is a spare and a want_replacement device, start replacement. cause md_check_recovery to call ->add_disk much more often. Instead of only when the array is degraded, it is now called whenever md_check_recovery finds anything useful to do, which includes updating the metadata for clean<->dirty transition. This causes unnecessary work, and causes info messages from ->add_disk to be reported much too often. So refine md_check_recovery to only do any actual recovery checking (including ->add_disk) if MD_RECOVERY_NEEDED is set. This fix is suitable for 3.3.y: Cc: stable@vger.kernel.org Reported-by: Jan Ceuleers <jan.ceuleers@computer.org> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud