Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx> writes: > A 'faulty' drive is being removed from a container after it has been > released by an array, however there is a race there. The drive is > released asynchronously by a monitor but sometimes it doesn't happen > before container checks it. It results in a container refusing to remove > a drive as it still seems to be a part of some array. > > It seems 'ping_monitor' could be a solution here to assure monitor has > had a chance to process the events, however it doesn't resolve the > problem - sometimes an array has to request a release of the drive few > times (as the array is busy) and single 'ping_monitor' call is not > sufficient. As there is no way to query monitor progress, it forces us > to retry a check several times before an error is returned. > > Signed-off-by: Tomasz Majchrzak <tomasz.majchrzak@xxxxxxxxx> > --- > Manage.c | 41 ++++++++++++++++++++++++++++------------- > 1 file changed, 28 insertions(+), 13 deletions(-) Looks good - 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
