summaryrefslogtreecommitdiffstats
path: root/drivers/md/raid0.c
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2007-07-12 17:29:15 +0100
committerLinus Torvalds <torvalds@woody.linux-foundation.org>2007-07-12 15:01:08 -0700
commitfc1ff9588a6d56258ff9576a31aa34f17757c666 (patch)
tree071fe0a07269c656448dc5dbe453eaa8e6f1a24a /drivers/md/raid0.c
parentf44db678edcc6f4c2779ac43f63f0b9dfa28b724 (diff)
downloadop-kernel-dev-fc1ff9588a6d56258ff9576a31aa34f17757c666.zip
op-kernel-dev-fc1ff9588a6d56258ff9576a31aa34f17757c666.tar.gz
dm raid1: handle log failure
When writing to a mirror, the log must be updated first. Failure to update the log could result in the log not properly reflecting the state of the mirror if the machine should crash. We change the return type of the rh_flush function to give us the ability to check if a log write was successful. If the log write was unsuccessful, we fail the writes to avoid the case where the log does not properly reflect the state of the mirror. A follow-up patch - which is dependent on the ability to requeue I/O's to core device-mapper - will requeue the I/O's for retry (allowing the mirror to be reconfigured.) Signed-off-by: Jonathan Brassow <jbrassow@redhat.com> Signed-off-by: Alasdair G Kergon <agk@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'drivers/md/raid0.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud