| 2010-01-07 12:39:51 |
Alvin |
bug |
|
|
added bug |
| 2010-01-14 13:17:19 |
Alvin |
tags |
|
ubuntu-boot-experience |
|
| 2010-01-14 13:19:01 |
Alvin |
tags |
ubuntu-boot-experience |
boot-experience |
|
| 2010-01-14 13:21:00 |
Alvin |
tags |
boot-experience |
ubuntu-boot-experience |
|
| 2010-02-05 16:43:29 |
Nikolaus Rath |
mountall (Ubuntu): status |
New |
Confirmed |
|
| 2010-02-05 16:56:39 |
Nikolaus Rath |
description |
Binary package hint: mountall
karmic: mountall 1.0
When mounting NFS shares at boot, there is always an error for each mount point:
mountall: Filesystem could not be mounted:
These errors appear, even when the filesystem will be mounted.
They also appear when they can't be mounted. (due to another bug)
Example:
mount.nfs4: DNS resolution failed for leto: Name or service not known
mountall: mount /home [901] terminated with status 32
mountall: Filesystem could not be mounted: /home
One or more of the mounts listed in /etc/fstab cannot yet be mounted:
(ESC for recovery shell)
/home: waiting for leto:/home
* Setting preliminary keymap
.... and so on
In this example, /home is mounted during the boot process, even though mountall says it could not be mounted. If it doesn't work, the same errors appear, but only the recovery shell is available. |
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. |
|
| 2010-02-05 16:58:20 |
Nikolaus Rath |
summary |
Inconsistent error message: Filesystem could not be mounted |
NFS mounts at boot time prevent boot or print spurious errors |
|
| 2010-03-03 07:46:02 |
Timo Aaltonen |
mountall (Ubuntu): importance |
Undecided |
Medium |
|
| 2010-03-03 07:46:02 |
Timo Aaltonen |
mountall (Ubuntu): milestone |
|
ubuntu-10.04 |
|
| 2010-03-03 07:46:19 |
Timo Aaltonen |
nominated for series |
|
Ubuntu Lucid |
|
| 2010-03-03 07:46:19 |
Timo Aaltonen |
bug task added |
|
mountall (Ubuntu Lucid) |
|
| 2010-03-31 16:05:24 |
Scott James Remnant (Canonical) |
mountall (Ubuntu Lucid): status |
Confirmed |
Fix Committed |
|
| 2010-03-31 18:40:10 |
Launchpad Janitor |
mountall (Ubuntu Lucid): status |
Fix Committed |
Fix Released |
|
| 2010-04-01 05:22:45 |
Paul McEnery |
attachment added |
|
img_0014.jpg http://launchpadlibrarian.net/42749690/img_0014.jpg |
|
| 2010-08-05 20:47:57 |
Gene Moreau |
bug |
|
|
added subscriber Gene Moreau |
| 2011-04-18 18:15:02 |
astrostl |
bug |
|
|
added subscriber astrostl |
| 2011-07-30 15:21:33 |
Damiön la Bagh |
attachment added |
|
Photo of the bug https://bugs.launchpad.net/ubuntu/+source/mountall/+bug/504224/+attachment/2242948/+files/2011-07-30%2013.47.13.jpg |
|
| 2011-11-19 19:04:19 |
susmita ghosh |
mountall (Ubuntu): assignee |
|
susmita ghosh (surja-bi-das) |
|
| 2011-11-19 19:22:34 |
Steve Langasek |
mountall (Ubuntu): assignee |
susmita ghosh (surja-bi-das) |
|
|
