If there's no rootfs entry in /etc/fstab, mountall never completes
Bug #1260368 reported by
Adam Conrad
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| mountall (Ubuntu) |
Triaged
|
Medium
|
Unassigned | ||
Bug Description
So, if there's no rootfs entry in fstab (or, in my case, nothing in fstab at all), mountall never gets around to remounting / read-write, never exits, and one's boot hangs there, patiently waiting for an event that will never be emitted.
Given that this appears to be literally the only thing an upstart/mountall system *needs* fstab for, I consider it a misfeature and/or flat-out bug that I had to add a root entry to fstab just for this.
Revision history for this message
| Steve Langasek (vorlon) wrote | #1 |
| Changed in mountall (Ubuntu): | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
To post a comment you must log in.
Given that there's already an entry in /lib/init/fstab for the root filesystem which is meant to be shadowed by whatever shows up in /etc/fstab, I agree.
There's lots of special-casing of the root filesystem in mountall, since it needs to be fscked before remounting rw, has a magic name in /proc/mounts, etc. So it's reasonable to fix this, but probably requires a bit of digging.