VirtualBox

Ticket #10676 (new defect)

Opened 22 months ago

Last modified 22 months ago

mount.vboxsf does not support generic userspace mount options (nofail)

Reported by: Speeddymon Owned by:
Priority: major Component: other
Version: VirtualBox 4.1.16 Keywords:
Cc: speeddymon@… Guest type: other
Host type: other

Description

Reference:  https://bugzilla.redhat.com/show_bug.cgi?id=832217

"The mount helpers (including /sbin/mount.vboxsf) have to support generic userspace mount options."

Guest OS: Fedora 17

I just 'yum upgrade'ed to the latest available kernel in Fedora 17, so the VirtualBox Extensions do not work after reboot until I can rebuild them again.

The problem I'm having is that I am now getting dumped into maintenance mode during boot, rather than being taken into the OS.

This happens because my share doesn't work due to the extensions not working. When I add 'nofail' to the mount options in /etc/fstab and then reboot without fixing the extensions, then I boot successfully but I still cannot access the share because of the fact that mount(8) wraps mount.vboxsf and mount.vboxsf doesn't support the generic mount options such as nofail.

When the next kernel comes out, I'm going to try using _netdev, but the fact of the matter is: mount.vboxsf should really support generic mount options.

Change History

comment:1 Changed 22 months ago by Speeddymon

Tested again using _netdev -- no issues whatsoever. Still would like to see generic mount option support in the mount.vboxsf command, however.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use