[Bug 1059522] Re: nfs not mounted during boot

[Torsten Bronger]

I don't really understand your comment, I'm afraid.  Anyway:  Even with
my static address setup there's a 1:5 chance that the home directory is
not mounted in time.  If I wait for DHCP, it is never mounted in time.
Then, the boot process simply fails, which mustn't happen.

I agree that mounting the home directory via NFS is a rare configuration
nowadays but it is useful in some situations as has ever been supported
by UNIX-flavoured systems, so I think Ubuntu should support it, too.

At some point in the boot process, the boot process must not continue
until all fstab mounts have been successful (of course, with a proper
timeout).  Currently, the NFS error is simply ignored and the mounting
is postponed.  In my opinion this is suboptimal behaviour.

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

Title:
  nfs not mounted during boot

Status in “nfs-utils” package in Ubuntu:
  New

Bug description:
  I mount my home directory via NFS from a server.  I boot directly into
  my account, so no login is necessary.  But then, my home directory is
  not yet mounted.  However, if I switch from DHCP to static IP, it is
  mounted properly.  Thus, network is setup too late in the boot
  process, so that NFS fails.

  Client: Ubuntu 12.04

  Line in /etc/fstab:
  192.168.178.24:/home/bronger /home/bronger nfs rsize=8192,wsize=8192,timeo=14,intr   0   0

  Excerpt of *working*/etc/network/interfaces:
  iface eth0 inet static
      address 192.168.178.20
      netmask 255.255.255.0
      gateway 192.168.178.1

  Excerpt of *non-working* /etc/network/interfaces:
  iface eth0 inet dhcp

  
  Server: Ubuntu 10.04

  Line in /etc/exports:
  /home/bronger     192.168.178.23(rw,sync,no_subtree_check,no_root_squash)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1059522/+subscriptions