[lucid] vboxsf mounts defined on /etc/fstab cause errors on boot: needs upstart job
Bug #530179 reported by
Sensiva
This bug affects 8 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
virtualbox-ose (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
I am runniing Lucid amd64 in vbox appliance, When I add vbox shared folders mounts in fstab, boot process stops (in both normal and recovery). I have to add noauto option to their lines to avoid this behaviour.
syntax I use : <sharname> <mountpoint> vboxsf
That didn't happen with any prior releases of Ubuntu.
Thank you
tags: | added: lucid mount.vboxsf vbox |
Changed in mountall (Ubuntu): | |
status: | Incomplete → Confirmed |
summary: |
- [lucid] Adding vboxsf in fstab stops boot process + [lucid] vboxsf causes a mount error on boot |
summary: |
- [lucid] vboxsf causes a mount error on boot + [lucid] vboxfs causes mount errors on boot |
summary: |
- [lucid] vboxfs causes mount errors on boot + [lucid] vboxsf mounts defined on /etc/fstab cause errors on boot |
Changed in virtualbox-ose (Ubuntu): | |
status: | New → Triaged |
importance: | Undecided → Medium |
tags: | added: upstart |
summary: |
- [lucid] vboxsf mounts defined on /etc/fstab cause errors on boot + [lucid] vboxsf mounts defined on /etc/fstab cause errors on boot: needs + upstart job |
To post a comment you must log in.
I have changed the package selection to mountall.