summaryrefslogtreecommitdiff
path: root/inventory
diff options
context:
space:
mode:
authorMariusz Tkaczyk <mariusz.tkaczyk@intel.com>2018-08-03 09:41:50 +0200
committerJes Sorensen <jsorensen@fb.com>2018-08-03 10:25:12 -0400
commitcb8f5371352f6c16af5aab8a40861e13aa50fc2b (patch)
tree118c3bc0b85c26e7ba958548f9f8e8c40194523b /inventory
parent84d88fd885de05a5f126a1f3661687c541001e39 (diff)
downloadmdadm-cb8f5371352f6c16af5aab8a40861e13aa50fc2b.tar.gz
Incremental: remove external arrays and devices correctly
Kernel returns EBUSY when device fail invokes array fail. In external metadata if kernel returns it, mdadm doesn't stop member arrays but it will try to stop container directly. It fails because container still has working arrays, so udev remove is triggered. Try to set faulty state on device in member arrays first. If kernel returns EBUSY, stop this array. After that remove the device from container. In external metadata mdmon has to remove faulty devices from degraded arrays, just remove device from container. Raid5 array doesn't return EBUSY, it allows to remove every device. Mdadm shouldn't block it. Signed-off-by: Mariusz Tkaczyk <mariusz.tkaczyk@intel.com> Signed-off-by: Jes Sorensen <jsorensen@fb.com>
Diffstat (limited to 'inventory')
0 files changed, 0 insertions, 0 deletions