Ubuntu
mountall package

bind or devpts mounts in /etc/fstab stop the boot process

Bug #524972 reported by Tim Gardner
24
This bug affects 4 people
Affects Status Importance Assigned to Milestone
mountall (Ubuntu)
Confirmed
Medium
Unassigned
Lucid
Won't Fix
Undecided
Unassigned

Bug Description

Binary package hint: mountall

Bind mounts in /etc/fstab appear to stop the boot process if the file system upon which they are mounted is also a DM RAID0 disk.
---
Architecture: amd64
DistroRelease: Ubuntu 10.04
InstallationMedia: Error: [Errno 13] Permission denied: '/var/log/installer/media-info'
Package: mountall 2.5
PackageArchitecture: amd64
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-14.20-server
Tags: lucid lucid
Uname: Linux 2.6.32-14-server x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

See original description
Tim Gardner (timg-tpi)
tags: added: regression-release
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Attached is /etc/fstab. Note that the machine booted OK after removing all bind and devpts mounts.

summary: - bind mount on a dm raid disk stop the boot process
+ bind or devpts mounts in /etc/fstab stop the boot process
Revision history for this message
Tim Gardner (timg-tpi) wrote : Dependencies.txt

apport information

tags: added: apport-collected
description: updated
Revision history for this message
Tim Gardner (timg-tpi) wrote :

You'll note that this machine doesn't actually have a DM RAID0 disk, which ought to simplify the bug.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Hmm, can't seem to reproduce this on a duo-core. The machine that exhibits the hang is a (2) CPU 6-core for a total of 24 threads.

Brian Murray (brian-murray)
Changed in mountall (Ubuntu Lucid):
assignee: nobody → Canonical Foundations Team (canonical-foundations)
Revision history for this message
frankie (frankie-etsetb) wrote :

Hi. I also noticed a similar problem in the boot process with lucid. If I have a missing partition in /etc/fstab. Lucid will show a message:

  "Waiting for /home2"

Four red dots will bright forever. and it won't continue booting.

Also, I am unable to recover from this situation. I tried ALT-F1, ESC, CTRL-ALT-F1.
I can't reach a terminal and I can't see the familiar prompt to single user or CTRL-D.

As you can see this is easy to reproduce, just add a wrong entry to /etc/fstab. Please let me know if that behaviour is unrelated and I should issue a new bug entry.

Revision history for this message
Steve Langasek (vorlon) wrote :

The message should say 'Waiting for /home2 [SM]'

If you hit "S", mountall will skip waiting for this device.

If you hit "M", you should be dropped to a maintenance shell.

I believe these messages should be expanded for release.

Revision history for this message
frankie (frankie-etsetb) wrote :

You gotta be kidding me, Steve !

Actually the message has that [SM]. I was wondering what it was. Keys S and M do what you said. It definitely should be more readable.

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Here is a bit more on my particular bind mount issue. Referring to the fstab in https://bugs.edge.launchpad.net/ubuntu/+source/mountall/+bug/524972/comments/1, I noted that all of the paths rooted on /usr3 were actually soft links. The actual path should be /home/usr3/... . When I made that change in /etc/fstab then everything worked fine, so the issue appears to be that mountall cannot resolve soft links at boot time.

Scott James Remnant (Canonical) (canonical-scott)
Changed in mountall (Ubuntu Lucid):
assignee: Canonical Foundations Team (canonical-foundations) → nobody
status: New → Won't Fix
Changed in mountall (Ubuntu):
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Scott James Remnant (Canonical) (canonical-scott) wrote :

Dear Reddit, the above does not mean I've marked it Won't Fix - it means I've moved the bug status back to tracking outside of Lucid since this is very unlikely to be fixed by the time Lucid releases ;-)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.