[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-03-08 Thread Brian Murray
** Changed in: multipath-tools (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (mathieu-tl)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-03-03 Thread Steve Baker
Trying to work around this for now I installed the older version on a
clean build of the server.

apt-get install multipath-tools=0.4.9-3ubuntu7 
apt-mark hold multipath-tools

This seemed to behave better at first, it boots without intervention for
instance, but it still seems some services are not seeing the multipath
device when they start up, even with a dependency on remote-filesystems
in upstart.

I'm also seeing a lot of these messages as the server is booting with
the older package version:

# dmesg | grep "failed to execute"
[3.042817] systemd-udevd[1155]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.056408] systemd-udevd[1176]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.058264] systemd-udevd[1219]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.060754] systemd-udevd[1230]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.062581] systemd-udevd[1238]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.064116] systemd-udevd[1243]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.065754] systemd-udevd[1249]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.068872] systemd-udevd[1265]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.069552] systemd-udevd[1268]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.071924] systemd-udevd[1270]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.077997] systemd-udevd[1291]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.081841] systemd-udevd[1306]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.084469] systemd-udevd[1319]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.088084] systemd-udevd[1337]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.092014] systemd-udevd[1355]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.095213] systemd-udevd[1365]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.097964] systemd-udevd[1375]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.100287] systemd-udevd[1383]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.102720] systemd-udevd[1392]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.119074] systemd-udevd[1400]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.121366] systemd-udevd[1424]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.123153] systemd-udevd[1428]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.123667] systemd-udevd[1429]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.128120] systemd-udevd[1438]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.140654] systemd-udevd[1456]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 
'socket:/org/kernel/dm/multipath_event': No such file or directory
[3.142887] systemd-udevd[1459]: failed to execute 
'/lib/udev/socket:/org/kernel/dm/multipath_event' 

[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-03-03 Thread Robie Basak
15:54  cyphermox: bug 1547206 claims a regression in a multipath-tools 
SRU I think. Please could 
   you take a look?

15:55  rbasak: yeah, I've already been in contact with tore
on that


** Tags added: regression-update

** Changed in: multipath-tools (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: multipath-tools (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-03-02 Thread Steve Baker
I am experiencing the same issue. I tried to work around the boot
problem by adding the nobootwait option in fstab, and the system is able
to boot that way, but I have been experiencing a plethora of issues with
other services that rely on the mounted filesystem failing
intermittently during boot.

Please let me know if I can provide any additional details to help.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-03-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: multipath-tools (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1547206] Re: Boot stalls on mountall "disk drive not ready" question in multipath-tools >= 0.4.9-3ubuntu7.5

2016-02-18 Thread Tore Anderson
After reviewing the changes between -3ubuntu7.4 and -3ubuntu7.5, I have
found that the problem is caused by the removal of the file
/lib/udev/rules.d/95-multipath.rules. In -3ubuntu7.4, it contained the
following:

#
# udev rules for multipathing.
# The persistent symlinks are created with the kpartx rules
#

# socket for uevents
RUN+="socket:/org/kernel/dm/multipath_event"

# Coalesce multipath devices before multipathd is running (initramfs, early
# boot)
ACTION=="add|change", SUBSYSTEM=="block", RUN+="/sbin/multipath -v0 /dev/$name"

If this file is manually reinstated (either to /lib/udev/rules.d or
/etc/udev/rules.d), boot is again successful (even with the latest
-3ubuntu7.9 multipath-tools package).

I see from the changelog that the removal was intentional:

  * debian/rules: don't ship 95-multipath.rules udev rules anymore; they are
not necessary with multipath-tools listening for udev events directly.
  * debian/multipath.udev: removed.

However, in order for this to actually work with multipath-backed "auto"
filesystems in /etc/fstab, it seems necessary to ensure that multipathd
is started before mountall runs. I am not entirely certain how to
accomplish this, though, as mountall is started from Upstart while
multipath-tools is stuck using a legacy SysV-init, and I do not know if
it is possible to enforce service ordering between the two init systems.
For what it's worth, renaming /etc/rcS.d/S21-multipath-tools-boot as
etc/rcS.d/S00-multipath-tools-boot does not work around the issue.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1547206

Title:
  Boot stalls on mountall "disk drive not ready" question in multipath-
  tools >= 0.4.9-3ubuntu7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1547206/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs