[Bug 798963] Re: Incorrect upstart dependencies cause race conditions with NFS mount points

[david]

Or a bit more verbose:

00:0a.0 Ethernet controller: nVidia Corporation MCP77 Ethernet (rev a2)
	Subsystem: ASUSTeK Computer Inc. Device 82e2
	Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 41
	Memory at fe02b000 (32-bit, non-prefetchable) [size=4K]
	I/O ports at d800 [size=8]
	Memory at fe02a000 (32-bit, non-prefetchable) [size=256]
	Memory at fe029000 (32-bit, non-prefetchable) [size=16]
	Capabilities: [44] Power Management version 2
	Capabilities: [50] MSI: Enable+ Count=1/16 Maskable+ 64bit+
	Capabilities: [6c] HyperTransport: MSI Mapping Enable+ Fixed+
	Kernel driver in use: forcedeth
	Kernel modules: forcedeth

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

Title:
  Incorrect upstart dependencies cause race conditions with NFS mount
  points

Status in “ifupdown” package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: mountall

  I use an NFS mounted home directory (in /etc/fstab: 192.168.0.2:/home
  /home      nfs
  defaults,tcp,async,noatime,rsize=16384,wsize=16384,_netdev) and
  automatic login in GDM. Usually, /home is not mounted when GDM tries
  to log in, causing various errors due to the non-existing /home
  directory.

  If I try again a few seconds later, all works fine (because by then
  /home is mounted).

  I think the upstart dependencies are wrong:
  - /etc/init/mountall.conf has no dependency on network, so it only mounts local file systems. However, it emits "filesystem" and "remote-filesystems"
  - /etc/init/gdm.conf depends on "filesystem" (obviously assuming that "filesystem" also includes network filesystems)

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