[Bug 1223745] Re: Dependency resolver causes hang on boot

[Steve Langasek]

On Thu, Sep 12, 2013 at 08:17:12AM -0000, Stefan Bader wrote:
> /mnt/cloud-images is nowait

Expected behavior; the mount point is outside of the "core" filesystem, so
mountall does not block the boot waiting for it by default.  You could mark
the filesystem 'bootwait' in /etc/fstab, in which case mountall would tag it
as 'remote' instead (... at least, that's what *should* happen!).

> ...
> local 4/4 remote 0/0 virtual 13/13 swap 1/1
> mounting event handled for /mnt/cloud-images
> mounting /mnt/cloud-images
> mount.nfs: Failed to resolve server nano: Name or service not known
> mountall: mount /mnt/cloud-images [1451] terminated with status 32
> Filesystem could not be mounted: /mnt/cloud-images
> mountall: Disconnected from Plymouth

Also expected behavior (and I think there's at least one other open bug
complaining about this).  mountall knows that this is a network mount, but
has no way to determine *which* network interface is required in order to
reach it, so it will retry the mount after each network interface comes
up... including lo.  So yes, this results in a bit of noise in the logs.

So all in all, I don't think there's anything here that explains the problem
on the other machine, which is specific to having the NFS mount under /home.

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

Title:
  Dependency resolver causes hang on boot

Status in “mountall” package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to version 2.50 I had my server hang on boot without
  any useful messages. I could track this to a NFS type mount in fstab
  which is mounted under /home and that is another mounted fs in fstab.
  Like

  /dev/xxx        /home          ext4  defaults          0 2
  xxx:/srv/img /home/img nfs    ro,nfsvers=3  0 0

  Verified that with mountall v2.49 this works (kind of as it seems to
  be done first time when network has not finished setting resolv.conf
  from the info DHCP returns). But at least boot finishes and by the
  time one can log in the nfs mount is done.

  Unlike with version 2.50 which either hangs, or when the mountpoint is
  moved somewhere under /, it boots but never mounts the NFS filesystem.

  Since one of the bigger changes from 2.49 is trying to do those
  dependant mounts in the right order I suspect this caused the current
  situation.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: mountall 2.49
  ProcVersionSignature: Ubuntu 3.11.0-7.13-generic 3.11.0
  Uname: Linux 3.11.0-7-generic x86_64
  .run.mount.utab:
   
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Wed Sep 11 11:17:22 2013
  InstallationDate: Installed on 2013-05-22 (111 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Alpha amd64 (20130521)
  MarkForUpload: True
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.11.0-7-generic root=UUID=638ccd94-ce45-46d9-b3f5-2e790862fd18 ro video=640x480 console=tty0 console=ttyS0,57600n8
  SourcePackage: mountall
  UpgradeStatus: No upgrade log present (probably fresh install)

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