Public bug reported:
Binary package hint: mountall
After upgrading a server to Ubuntu 10.04, I found it hanging early in
the boot process with no error messages. Eventually I discovered the
the problem: entries in fstab that have a first field (fs_spec) which
starts with the name of a filesystem type caused the boot to hang.
Renaming or simply prefixing them to avoid clashes with a filesystem
type avoided the problem.
So for example, the following fstab would hang during boot:
| proc /proc proc defaults 0 0
| UUID=e8e54459-86eb-41f9-ae03-a8c576fb0c9d / ext3 noatime,errors=remount-ro 0 1
| UUID=dbe2dc82-a339-4b86-b1e6-de1060e09845 none swap sw 0 0
| proc-epic-i386 /srv/epic.canonical.com/chroot-i386/proc proc defaults 0 0
| devpts-epic-i386 /srv/epic.canonical.com/chroot-i386/dev/pts devpts
defaults 0 0
While the following works:
| proc /proc proc defaults 0 0
| UUID=e8e54459-86eb-41f9-ae03-a8c576fb0c9d / ext3 noatime,errors=remount-ro 0 1
| UUID=dbe2dc82-a339-4b86-b1e6-de1060e09845 none swap sw 0 0
| lolproc-epic-i386 /srv/epic.canonical.com/chroot-i386/proc proc defaults 0 0
| loldevpts-epic-i386 /srv/epic.canonical.com/chroot-i386/dev/pts devpts
defaults 0 0
Arguably our use of fs_spec is 'out of spec' (sorry), but FWIW I've
been doing this for years on both Debian and Ubuntu systems and I've
not run into a problem with it until now. In any event, silently
hanging on boot is a fairly user hostile way to react and (IMO) a bug,
regardless of the validity of our use of fs_spec.
** Affects: mountall (Ubuntu)
Importance: Undecided
Status: New
** Tags: regression-potential
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/695404
Title:
mountall hangs boot if first field of an fstab entry starts with the name of
a filesystem
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
