[Bug 621336] Re: Mount failure causes boot hang

[Steve Langasek]

> If the filesystem isn't critical, boot should continue as normal.

That's true, but the definition of a "critical" filesystem is system-
dependent.

If you want boot to continue without waiting for a given filesystem, you
need to mark the mount as 'nobootwait' in /etc/fstab in the options
field.

The current behavior is by design, as it's the only way to get robust
booting by default from the system, and no changes will be made to
upstart to deviate from this.  Therefore closing this bug report as
invalid.

** Changed in: upstart (Ubuntu)
       Status: New => Invalid

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

Title:
  Mount failure causes boot hang

Status in “upstart” package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: upstart

  Lucid 10.04 Server

  Using curlftpfs fuse filesystem within /etc/fstab
  If you set the "auto" option to mount automatically at boot
  boot stalls, with plymouth sitting there waiting for user input (S to skip mount, M for manual mount)

  This is crippling on a server

  I've resorted to using "noauto" in fstab, and a script in
  /etc/rc.local to sleep for 10 secs, then mount curlftpfs

  Could upstart be modified to not stall on non-boot-essential mount failures?
  (at least finish boot and start sshd)

  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: upstart 0.6.5-7
  ProcVersionSignature: Ubuntu 2.6.32-24.41-generic-pae 2.6.32.15+drm33.5
  Uname: Linux 2.6.32-24-generic-pae i686
  Architecture: i386
  Date: Fri Aug 20 19:37:24 2010
  ProcEnviron:
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: upstart

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