| 1 | | For the test case. |
| 2 | | |
| 3 | | Before vboxsf share(s) mounting, bind root somewhere else : mount --bind / /var/local/bind/root. |
| 4 | | Do some stuff ... (optionally, part of init ) |
| 5 | | Now mount vboxsf shares , as with the vboxadd service |
| 6 | | After such mount, you will have these shares at two places : original configured , and under the root bind. As e.g.: |
| 7 | | |
| 8 | | {{{ |
| 9 | | dloads on /media/sf_dloads type vboxsf (rw,nodev,relatime) |
| 10 | | dloads on /var/local/bind/root/media/sf_dloads type vboxsf (rw,nodev,relatime) |
| 11 | | }}} |
| 12 | | |
| 13 | | Then you can test the original command "umount -a -t vboxsf", and confirm it fails after first unmount of same share, returns non 0 (32 for me) |
| 14 | | |
| 15 | | My guest : Linux Fedora 29, x86_64, |
| 16 | | |
| 17 | | {{{ |
| 18 | | umount --version |
| 19 | | umount from util-linux 2.32.1 (libmount 2.32.1: selinux, btrfs, assert, debug) |
| 20 | | }}} |
| 21 | | |
