summaryrefslogtreecommitdiffstats
path: root/drivers/net
diff options
context:
space:
mode:
authorNeilBrown <neilb@suse.de>2009-11-13 07:47:00 +0100
committerNeilBrown <neilb@suse.de>2009-11-13 07:47:00 +0100
commitc148ffdcda00b6599b70f8b65e6a1fadd1dbb127 (patch)
tree3d50cc9dbef926f62a588dc1f45f1df304e1bf31 /drivers/net
parentDon't unconditionally set in_sync on newly added device in raid5_reshape (diff)
downloadlinux-c148ffdcda00b6599b70f8b65e6a1fadd1dbb127.tar.xz
linux-c148ffdcda00b6599b70f8b65e6a1fadd1dbb127.zip
md/raid5: Allow dirty-degraded arrays to be assembled when only party is degraded.
Normally is it not safe to allow a raid5 that is both dirty and degraded to be assembled without explicit request from that admin, as it can cause hidden data corruption. This is because 'dirty' means that the parity cannot be trusted, and 'degraded' means that the parity needs to be used. However, if the device that is missing contains only parity, then there is no issue and assembly can continue. This particularly applies when a RAID5 is being converted to a RAID6 and there is an unclean shutdown while the conversion is happening. So check for whether the degraded space only contains parity, and in that case, allow the assembly. Signed-off-by: NeilBrown <neilb@suse.de>
Diffstat (limited to 'drivers/net')
0 files changed, 0 insertions, 0 deletions