summaryrefslogtreecommitdiff
path: root/drivers/md/raid1.c
diff options
context:
space:
mode:
authorJonathan Brassow <jbrassow@redhat.com>2012-05-22 03:55:30 (GMT)
committerNeilBrown <neilb@suse.de>2012-05-22 03:55:30 (GMT)
commit81f382f9e0b25ef56b1c0283c900b86b91a5e4c7 (patch)
tree992f754485b3f78503b7e4f68835da4438786c09 /drivers/md/raid1.c
parent47525e59e40ffb8cbc944c0055e9c4902cd3ee99 (diff)
downloadlinux-fsl-qoriq-81f382f9e0b25ef56b1c0283c900b86b91a5e4c7.tar.xz
DM RAID: Record and handle missing devices
Missing dm-raid devices should be recorded in the superblock When specifying the devices that compose a DM RAID array, it is possible to denote failed or missing devices with '-'s. When this occurs, we must record this in the superblock. We do this by checking if the array position's data device is missing and then forcing MD to record the superblock by setting 'MD_CHANGE_DEVS' in 'raid_resume'. If we do not cause the superblock to be rewritten by the resume function, it is possible for a stale superblock to be written by an out-going in-active table (during 'raid_dtr'). Signed-off-by: Jonathan Brassow <jbrassow@redhat.com> Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/md/raid1.c')
0 files changed, 0 insertions, 0 deletions