summaryrefslogtreecommitdiffstats
path: root/drivers/md/Kconfig
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2011-12-08 16:27:57 +1100
committerNeilBrown <neilb@suse.de>2011-12-08 16:27:57 +1100
commit9283d8c5af4cdcb809e655acdf4be368afec8b58 (patch)
treed4baa86260792a10782808e51d5468e145358980 /drivers/md/Kconfig
parent8bd2f0a05b361e07d48bb34398593f5f523946b3 (diff)
downloadtalos-op-linux-9283d8c5af4cdcb809e655acdf4be368afec8b58.tar.gz
talos-op-linux-9283d8c5af4cdcb809e655acdf4be368afec8b58.zip
md/raid5: never wait for bad-block acks on failed device.
Once a device is failed we really want to completely ignore it. It should go away soon anyway. In particular the presence of bad blocks on it should not cause us to block as we won't be trying to write there anyway. So as soon as we can check if a device is Faulty, do so and pretend that it is already gone if it is Faulty. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/Kconfig')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud