[Bug 1233610] Re: boot process hangs very often when NFS shares are used

[Zygmunt Krynicki]

About a dozen reboots later I can say that it's not working.

I tried a few simplifications:

1) Try with my vanilla /etc/fstab -> hangs all the time (I never got to boot to desktop this way)
2) Drop everything but home (but keep 'bootwait') -> worked once (just typing this now), needs more testing to see if this is stable
3) Drop everything but home (also drop 'bootwait') -> this feels like a regression over the previous state (precise packages). I would hang about 70% of the time I've tried it. If it managed to boot to desktop /home would not be mounted! IIRC mountall in precise automatically adds 'bootwait' for /home, is this not the case in quantal?

I also got a case that feels like something else is affecting this. With
just /home (without bootwait then) I got to the step where everything
was mounted but apparently mountall didn't say it was "done". Looking at
the log file I see that mountall could not talk to plymouth. I have a
log file to show:

** Attachment added: "mountall.log with one remote share (that got mounted) but no progress, stuck before lightdm"
   https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/1233610/+attachment/3863775/+files/mountall.mounted-but-failed-to-continue.log

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

Title:
  boot process hangs very often when NFS shares are used

Status in “mountall” package in Ubuntu:
  New

Bug description:
  I'm running up-to-date Ubuntu 12.04.3 with the 3.2 kernel. I have a
  FreeNAS box exporting a number of NFS shares. My machine can boot
  once-in-a-while but I have problems on practically every boot, that I
  need to resolve by rebooting and trying again.

  My fstab:

  # /etc/fstab: static file system information.
  proc            /proc           proc    nodev,noexec,nosuid 0       0
  UUID=2f6ca502-9419-4040-a702-2c9dc716dbc5 /               ext4    errors=remount-ro 0       1
  nodev /ramdisk tmpfs defaults 0 0
  silverbox:/mnt/vol1/software /nas/software nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol1/videos /nas/videos nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/backup /nas/backup nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/home /home nfs auto,exec 0 0 # ENROLL
  silverbox:/mnt/vol4/source /home/zyga/source nfs auto 0 0 # ENROLL
  silverbox:/mnt/vol4/steam /nas/steam nfs auto,bootwait 0 0 # ENROLL
  silverbox:/mnt/vol4/music /nas/music nfs auto,bootwait 0 0 # ENROLL
  silverbox:/mnt/vol4/photos /nas/photos nfs auto,bootwait 0 0 # ENROLL

  The network between the two boxes is working perfectly over gigabit
  wired connection. I can always mount each share explicitly, it only
  causes failures a boot. My local network uses openwrt routers and has
  correct DNS setup for each machine.

  My desktop (the machine affected by this bug) uses network manager
  with DHCP connection but I did try static IP before and it had no
  effect on the failure rate.

  I've added a way to open an emergency tty (patched /etc/init/tty6.conf
  to start on startup) and inspected mountall logs (patched
  mountall.conf to have --debug, not have --verbose, have console log
  and not 'expect daemon'). I'll attach /var/log/mountall.log from a
  successful boot below.

  I have tried to debug this issue with jodh and xnox on #ubuntu-devel
  and got asked to report this and wait for slangasek. I can freely
  reproduce this bug and I can assist in debugging if required.

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