diff options
author | NeilBrown <neilb@suse.de> | 2010-03-31 11:21:44 +1100 |
---|---|---|
committer | NeilBrown <neilb@suse.de> | 2010-05-18 15:27:57 +1000 |
commit | e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd (patch) | |
tree | ea9c8e548c4d5eb5fc903bab05af3bda4192ed00 /arch/sh/drivers | |
parent | d754c5ae1ff76b20d3ecde8ad666d7865eada8ae (diff) | |
download | kernel_samsung_aries-e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd.zip kernel_samsung_aries-e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd.tar.gz kernel_samsung_aries-e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd.tar.bz2 |
md/raid1: delay reads that could overtake behind-writes.
When a raid1 array is configured to support write-behind
on some devices, it normally only reads from other devices.
If all devices are write-behind (because the rest have failed)
it is possible for a read request to be serviced before a
behind-write request, which would appear as data corruption.
So when forced to read from a WriteMostly device, wait for any
write-behind to complete, and don't start any more behind-writes.
Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'arch/sh/drivers')
0 files changed, 0 insertions, 0 deletions