aboutsummaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2008-08-05 01:54:13 -0400
committerNeilBrown <neilb@suse.de>2008-08-05 01:56:32 -0400
commitac4090d24c6a26211bc4523d920376e054d4f3f8 (patch)
tree5aabdbb2448967cbfc23be2fa6714d1c1bbf29dc /virt
parentdba034eef2456d2a9f9a76806846c97acf6c3ad1 (diff)
Don't let a blocked_rdev interfere with read request in raid5/6
When we have externally managed metadata, we need to mark a failed device as 'Blocked' and not allow any writes until that device have been marked as faulty in the metadata and the Blocked flag has been removed. However it is perfectly OK to allow read requests when there is a Blocked device, and with a readonly array, there may not be any metadata-handler watching for blocked devices. So in raid5/raid6 only allow a Blocked device to interfere with Write request or resync. Read requests go through untouched. raid1 and raid10 already differentiate between read and write properly. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions