Opened 8 years ago
Closed 8 years ago
#16670 closed defect (fixed)
mount.vboxsf symlink broken
Reported by: | chr.moench-tegeder | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 5.1.20 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | all |
Description
This looks like a regression in 5.1.20.
Guest system is Linux - reproduced with both Debian 8 and openSUSE 42.2. After upgrading Guest Additions from 5.1.18, the /sbin/mount.vboxsf symlink points to the wrong location:
root@host1:~# ls -l /sbin/mount.vboxsf lrwxrwxrwx 1 root root 49 Apr 19 10:33 /sbin/mount.vboxsf -> /opt/VBoxGuestAdditions-5.1.20/other/mount.vboxsf root@host1:~# find /opt/VBoxGuestAdditions-5.1.20/ -name mount\* /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf
With previous versions of the Guest Additions (checked 5.1.18 and 5.1.14, that's what I have around currently), /sbin/mount.vboxsf points to /usr/lib{64,/x86_64-linux-gnu}/VBoxGuestAdditions/mount.vboxsf (exact location of the lib64 directory varies per linux distribution, examples taken from CentOS 7 and Debian 8).
A quick test for stale symlinks (find -L / -xdev -type l) shows that mount.vboxsf is the only file affected. This allows for the simple workaround of fixing the symlink: root@host1:~# ln -sf /usr/lib/x86_64-linux-gnu/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf
(remember to check the lib64 path for your distribution, e.g. lib64 on Redhat/Centos-based distributions)
Change History (6)
comment:1 by , 8 years ago
comment:2 by , 8 years ago
Confirmed. The slightly more correct fix is
ln -sf /opt/VBoxGuestAdditions-5.1.20/lib/VBoxGuestAdditions/mount.vboxsf /sbin/mount.vboxsf
Or even better more complete, edit line 429 of /sbin/rcvboadd and change it to
ln -sf "$lib_path/$PACKAGE/mount.vboxsf" /sbin
comment:3 by , 8 years ago
The latest 5.1.x Guest Additions test build which can be downloaded from here should also fix the problem.
comment:5 by , 8 years ago
Fixes issue #16680 Vbox-5.1.20 mount -t vboxsf returns sf_read_super_aux err=-22
Hmpf, that killed the formatting. Alas, the wrong symlink as observed on openSUSE and Debian:
and the workaround for the same systems (other distributions, notably Centos-like, may have other locations for lib64):