[Bug 964207] Re: Dependency loops due to ANDed start conditions leave system unbootable

[Nikolaus Rath]

fstab looks like this:

proc            /proc           proc    nodev,noexec,nosuid 0       0
/dev/mapper/vg0-fat_client     /               ext4    relatime,errors=remount-ro 0       1
/dev/mapper/vg0-swap    none            swap    sw              0       0
spitzer:/opt /opt        nfs4    auto 0  0
spitzer:/home /home          nfs4    auto 0  0

With this setup, /opt and /home are mounted by mountall, however, they
are mounted with the wrong clientaddr:

$ mount | grep nfs
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
spitzer:/home on /home type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2)
spitzer:/opt on /opt type nfs4 (rw,clientaddr=0.0.0.0,addr=192.168.1.2)

Since this happens on all clients (they all get same clientaddr), this
results in a frozen mount (cf
http://thread.gmane.org/gmane.linux.nfs/47780)

If I remount manually, the clientaddr is correct, so I believe mountall
is attempting to mount this too early.

Should I report this as a separate bug?

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

Title:
  Dependency loops due to ANDed start conditions leave system unbootable

Status in “mountall” package in Ubuntu:
  Invalid
Status in “upstart” package in Ubuntu:
  Invalid

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/mountall/+bug/964207/+subscriptions