Re: [dm-devel] [PATCH v2 08/10] multipathd: handle repeated udev retrigger failure

2018-10-23 Thread Benjamin Marzinski
On Tue, Oct 23, 2018 at 03:43:46PM +0200, Martin Wilck wrote: > If a path was still not properly initialized after exhausting the > retrigger tries, it used to remain in INIT_MISSING_UDEV state forever. > get_uid() might fall back to non-udev-based methods to determine > the WWID, but it would

[dm-devel] [PATCH v2 08/10] multipathd: handle repeated udev retrigger failure

2018-10-23 Thread Martin Wilck
If a path was still not properly initialized after exhausting the retrigger tries, it used to remain in INIT_MISSING_UDEV state forever. get_uid() might fall back to non-udev-based methods to determine the WWID, but it would never be called for a path in this state any more. This patch changes