| commit | 4fc8a6cf7b5657cacd6e28d6699950dd00eb5bbb | |
| author | NeilBrown <neilb@suse.de> | |
| Wed, 31 Mar 2010 00:21:44 +0000 (31 11:21 +1100) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 13 Aug 2010 20:27:37 +0000 (13 13:27 -0700) | ||
| tree | 992c63a89f596ae2864704d163392d37080cd5e6 | treesnapshot (tar.gz zip) |
| parent | d2ec7f89bbbbbe6803e34a499e05c5896ec84803 | commitdiff |
md/raid1: delay reads that could overtake behind-writes.
commit e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
commit e555190d82c0f58e825e3cbd9e6ebe2e7ac713bd upstream.
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>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
| drivers/md/bitmap.c | diffblobblamehistory | |
| drivers/md/bitmap.h | diffblobblamehistory | |
| drivers/md/raid1.c | diffblobblamehistory |