On 12/06/2016 04:22 PM, Benjamin Marzinski wrote:
> On Tue, Dec 06, 2016 at 04:11:42PM +0100, Xose Vazquez Perez wrote:
>> On 10/29/2016 04:55 AM, Benjamin Marzinski wrote:
>>
>>> Multipathd uses retrigger_tries to give udev more chances to to fill in
>>> the uid_attribute, so that the path
On Tue, Dec 06, 2016 at 04:11:42PM +0100, Xose Vazquez Perez wrote:
> On 10/29/2016 04:55 AM, Benjamin Marzinski wrote:
>
> > Multipathd uses retrigger_tries to give udev more chances to to fill in
> > the uid_attribute, so that the path device is correctly set up in the
> > udev database.
On 10/29/2016 04:55 AM, Benjamin Marzinski wrote:
> Multipathd uses retrigger_tries to give udev more chances to to fill in
> the uid_attribute, so that the path device is correctly set up in the
> udev database. However the multipath command can't do this, so it should
> just immediately give up
On 10/29/2016 04:55 AM, Benjamin Marzinski wrote:
Multipathd uses retrigger_tries to give udev more chances to to fill in
the uid_attribute, so that the path device is correctly set up in the
udev database. However the multipath command can't do this, so it should
just immediately give up on
Multipathd uses retrigger_tries to give udev more chances to to fill in
the uid_attribute, so that the path device is correctly set up in the
udev database. However the multipath command can't do this, so it should
just immediately give up on udev, and try to get the wwid directly.
Signed-off-by:
