NFS mounts at boot time prevent boot or print spurious errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: mountall
karmic: mountall 1.0
When mounting NFS shares at boot, the first mount attempt usually fails since rpc or portmap are not running, or the network itself is not up yet.
These errors appear although the filesystem will be mounted successfully later on, so the user cannot distinguish them from "real" mount failures that need intervention by the admin.
Even worse, when the NFS mounts happen to be for a mountpoint that mountall considers essential for boot (like /home), the user is dropped to an emergency shell and system refuses to boot.
A temporary workaround is to add "nobootwait" for the affected mountpoints, but this causes the system to continue booting even if the mountpoint is not available when the network is set up correctly, i.e. if there is a real problem with the NFS server.
Proposed fix:
mountall should not try to mount any network file systems when called the first time. Only when the network is up and mountall receives SIGUSR1 it should try to do so. If this does not work at *that* point, mountall should print an error (and stop the boot for essential mount points) as before.
tags: | added: ubuntu-boot-experience |
tags: |
added: boot-experience removed: ubuntu-boot-experience |
tags: |
added: ubuntu-boot-experience removed: boot-experience |
description: | updated |
summary: |
- Inconsistent error message: Filesystem could not be mounted + NFS mounts at boot time prevent boot or print spurious errors |
Changed in mountall (Ubuntu): | |
importance: | Undecided → Medium |
milestone: | none → ubuntu-10.04 |
Changed in mountall (Ubuntu Lucid): | |
status: | Confirmed → Fix Committed |
Changed in mountall (Ubuntu): | |
assignee: | nobody → susmita ghosh (surja-bi-das) |
Changed in mountall (Ubuntu): | |
assignee: | susmita ghosh (surja-bi-das) → nobody |
For clarification, if this is the same thing I'm having it's preventing my machine from booting.
I have about 10 NFS mounts, and my machine hangs on boot with the above printouts.
To work around this, and boot into X so I can log in, I can enter the recovery shell, do "mount -a", and exit the recovery shell.
This enables me to boot into X. I still cannot access my virtual text consoles after this; I assume that the boot process is still waiting for something else...