[Bug 964207] Re: Hanging mountall stops boot process

[Nikolaus Rath]

Since this is triggered by changing an upstart job unrelated to
mountall, I'm reassigning this to upstart.

** Description changed:

- One of my Lucid systems stopped booting. If I interpret the "initctl
- list" output correctly (attached) the system is waiting for mountall to
- complete.
+ If /home is mounted on a separate partition, and the gdm start condition
+ in /etc/init/gdm.conf is modified to include "mounted MOUNTPOINT=/home"
+ as follows:
  
- mountall, however, seems just stuck doing nothing. I added --verbose to
- /etc/init/mountall.conf and redirected the output into a file (attached
- as well).
+ start on (filesystem
+           and mounted MOUNTPOINT=/home
+           and started dbus
+           and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
+                or stopped udevtrigger))
  
- If I execute another "mountall --verbose", this one seems to complete
- and the system continues booting. I have attached the output of this
- second run as well.
+ then a lucid system will no longer boot. It seems that in this case the
+ mountall process is waiting for input from upstart, but upstart is not
+ sending anything. Thus, the required muntall events are not emitted and
+ the system refuses to boot.
+ 
+ The problem can be worked around by manually starting another mountall
+ instance while the first instance is hanging.
+ 
+ I have attached the --verbose output of the first and second mountall, as
+ well as an strace output.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mountall 2.15.3
  ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-server 3.0.22
  Uname: Linux 3.0.0-17-server x86_64
  Architecture: amd64
  Date: Sat Mar 24 18:45:46 2012
  ProcEnviron:
-  PATH=(custom, user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: mountall

** Package changed: mountall (Ubuntu) => upstart (Ubuntu)

** Summary changed:

- Hanging mountall stops boot process
+ Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot

** Summary changed:

- Waiting for mounted MOUNTPOINT=/home in gdm.conf breaks system boot
+ Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot

** Summary changed:

- Waiting for "mounted MOUNTPOINT=/home in gdm.conf" breaks system boot
+ Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to mountall in Ubuntu.
https://bugs.launchpad.net/bugs/964207

Title:
  Waiting for "mounted MOUNTPOINT=/home" in gdm.conf breaks system boot

Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  If /home is mounted on a separate partition, and the gdm start
  condition in /etc/init/gdm.conf is modified to include "mounted
  MOUNTPOINT=/home" as follows:

  start on (filesystem
            and mounted MOUNTPOINT=/home
            and started dbus
            and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
                 or stopped udevtrigger))

  then a lucid system will no longer boot. It seems that in this case
  the mountall process is waiting for input from upstart, but upstart is
  not sending anything. Thus, the required muntall events are not
  emitted and the system refuses to boot.

  The problem can be worked around by manually starting another mountall
  instance while the first instance is hanging.

  I have attached the --verbose output of the first and second mountall, as
  well as an strace output.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: mountall 2.15.3
  ProcVersionSignature: Ubuntu 3.0.0-17.30~lucid1-server 3.0.22
  Uname: Linux 3.0.0-17-server x86_64
  Architecture: amd64
  Date: Sat Mar 24 18:45:46 2012
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: mountall

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/964207/+subscriptions