** Description changed: 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) + 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. - 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 + 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. - 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. + 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.
** Summary changed: - Inconsistent error message: Filesystem could not be mounted + NFS mounts at boot time prevent boot or print spurious errors -- NFS mounts at boot time prevent boot or print spurious errors https://bugs.launchpad.net/bugs/504224 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
