Bug#859157: multipath-tools: after bootup multipathd timeout on commands - requires daemon restart

[Alban Browaeys]

Le jeudi 06 avril 2017 à 19:25 +0530, Ritesh Raj Sarraf a écrit :
> Since I haven't been able to reproduce this locally, can we close
> this ?
> I feel this issue may also be a side effect, because of the other
> issue you had
> reported.

I pushed the issue upstream as you suggested (this afternoon :)
https://marc.info/?t=149148165900001&r=1&w=2

> If you agree, please go ahead and mark this closed.

This bug is not a local issue even if unlikely to affect most users.

>From https://marc.info/?l=dm-devel&m=149142931410122&w=2 multipath
service starts after udevadm triggered, so most devices do not trigger
the udev codepath from multipath. 
But bcache0 manages to. 

I have not managed to sort out why as of now.
I have only been able to see that bcache0 is only detected at boot.
If I use a "fixed" multipathd, bcache0 shows in the paths (even though
not functional as a multipath path I believe)... but does not if I
restart multipathd.
It could be that bcache device are not meant to work with multipath ...
if so could bcache devices get blacklisted ?
I wonder if another bug report (upstream) is of need.


About this bug, would you include a patch for this non critical issue ?
Else this bug could get close.
Next release will be fixed against this issue.

Best regards
Alban