Package: open-iscsi
Version: 2.0.873+git0.3b4b4500-8+deb8u1
Severity: normal
Owner: !
Tags: jessie moreinfo
Hi there,
FYI: I'm co-maintainer of open-iscsi in Debian, but not
multipath-tools. CC'ing the bugtracker, assigning to open-iscsi for
now, will reassign to multipath-tools later if necessary.
Am 2016-04-22 14:45, schrieb Cédric Bassaget:
After a reboot, iscsi targets are OK, but multipath does not show any
volume. I have to restart it by hand to bring the multipath volume up.
Gah. During the freeze of Jessie I encountered some bugs related to the
boot process and I thought we had fixed them all before Jessie was
released. Obviously not... :-(
I guess it's because on system startup, multipath-tools is launched
befors open-iscsi. open-iscsi seems to be systemd compliant, but not
multipath-tools.
For current versions (starting with Jessie) of multipath-tools, this
is correct, as the daemon is supposed to be started and then pick up
all of the devices as they appear dynamically.
OTOH, what you're seeing in dmesg is just the modules that are loaded,
which might be due to /etc/modules, /etc/modprobe.d or similar, so
they don't necessarily indicate which is started before.
root@virtm6:/etc# find rc?.d -name 'S*multipath-tools'
rc2.d/S02multipath-tools
rc3.d/S02multipath-tools
rc4.d/S02multipath-tools
rc5.d/S02multipath-tools
multipath-tools is still late-boot? That seems wrong to me. May be part
of the problem you're seeing.
Could you give me the output of the following on your system?
systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires multipath-tools.service
systemctl show -p Before,After,WantedBy,Wants,RequiredBy,Requires open-iscsi.service
Also, what does the following command tell you? (After booting, when
the problem appears, but before restarting multipath to fix it.)
journalctl -u open-iscsi.service -u multipath-tools.service
What would be the best way to fox this problem ?
Well, there's probably still some bug in the integration between
open-iscsi and multipath-tools. The output of the commands I requested
will help me narrow down the problem, which will then hopefully give
me enough information to tell you how to fix it on your local system,
and hopefully this can be fixed in 8.5.
Regards,
Christian