Re: [PATCH] Incremental: remove external arrays and devices correctly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/03/2018 03:41 AM, Mariusz Tkaczyk wrote:
> 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@xxxxxxxxx>

Applied!

Thanks,
Jes


--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux RAID Wiki]     [ATA RAID]     [Linux SCSI Target Infrastructure]     [Linux Block]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device Mapper]     [Device Mapper Cryptographics]     [Kernel]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Yosemite Forum]


  Powered by Linux