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

[Steve Langasek]

> When this interface gets configured, it is in the "UP" state, but it takes 1-2
> seconds to get into the "RUNNING" state.

What is the ethernet hardware of this machine?

This is not a bug in mountall, but in the bits that signal to mountall
that the interface is ready before it is - so somewhere in ifupdown +
upstart + udev + kernel.

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

** Changed in: ifupdown (Ubuntu)
   Importance: Undecided => Medium

** Changed in: ifupdown (Ubuntu)
       Status: New => Incomplete

-- 
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