the patch removes the warning but still, something isn't right --
multipathd does not show the devices that shoul've been created by the
udev rule. we're gathering more information and will update soon.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which
multipathd does not act upon udev changes -- its very easy to see when
running udev monitor and multipathd -v9 -d and then attaching new disks.
by the looks of it, support for monitoring events by libudev was only added in
2013, far later than 0.4.9
everything seems to exist in 0.5, and none of
the patch removes the warning but still, something isn't right --
multipathd does not show the devices that shoul've been created by the
udev rule. we're gathering more information and will update soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
multipathd does not act upon udev changes -- its very easy to see when
running udev monitor and multipathd -v9 -d and then attaching new disks.
by the looks of it, support for monitoring events by libudev was only added in
2013, far later than 0.4.9
everything seems to exist in 0.5, and none of
With the mainline kernel, 'modprobe lpfc' doesn't exit:
https://gist.github.com/e1d29ee22d54372a7a5e38b2c0b6a21b
** Tags added: kernel-bug-exists-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi,
Amit is on vacation for the following week, so I ran the test again with
'4.4.0-36-generic #55~lp1622894' and the sg device gets created when the alua
driver is loaded:
https://gist.github.com/2c1a1f9f81262fa8e490877e91bade95
but when I remove the lpfc driver there's still a stack trace in
We haven't tested v4.4.0-30 since there's no deb package for it (I guess
it was removed from the repo?).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1622894
Title:
sg devices are not being
