Opened 5 years ago
Closed 5 years ago
#19430 closed defect (worksforme)
FreeBSD 12.1: vboxvfs filesystem problems
Reported by: | npapadon | Owned by: | |
---|---|---|---|
Component: | guest additions | Version: | VirtualBox 6.0.16 |
Keywords: | Cc: | ||
Guest type: | BSD | Host type: | Mac OS X |
Description
I'm able to install the drivers and mount, however it looks like the filesystem may be having problems. I get two different results with mtree and also am having errors checking out a Git repo over vboxvfs.
I mounted the same file system over NFS from my Mac and there are no issues.
sudo mount -t vboxvfs -o uid=1001 Source /mnt/srcr
FreeBSD 12.1-RELEASE r354233
I will attach the results of mtree.
Attachments (4)
Change History (9)
by , 5 years ago
comment:1 by , 5 years ago
I compared the results with three configurations. It appears the results over vboxvfs driver mounted filesystem differ in that they are missing the “nlink=X” field. size is also missing, but I’m assuming that’s expected.
$ diff mtreenfs-mount.txt mtreeonmac.txt|more < branches type=dir nlink=2 time=1547439167.000000000 ---
branches type=dir nlink=2 size=64 time=1547439167.000000000
diff mtreenfs-mount.txt mtree-fbsd-vboxvfs.txt |less < branches type=dir nlink=2 time=1547439167.000000000 ---
branches type=dir time=1547439167.000000000
Perhpas the missing nlink is the problem?
Thanks
comment:2 by , 5 years ago
I compared the results between configurations of same directory tree. Using mounted filesystem with vboxvfs, using filesystem directly on Mac, using NFS mounted filesystem. All of the same data.
It appears the results over the vboxvfs driver mounted filesystem differ in that vboxvfs mount is missing the “nlink=X” field. size is also missing, but I’m assuming that’s expected as it’s missing on the nfs mount as well.
$ diff mtreenfs-mount.txt mtreeonmac.txt|more < branches type=dir nlink=2 time=1547439167.000000000 ---
branches type=dir nlink=2 size=64 time=1547439167.000000000
diff mtreenfs-mount.txt mtree-fbsd-vboxvfs.txt |less < branches type=dir nlink=2 time=1547439167.000000000 ---
branches type=dir time=1547439167.000000000
Perhaps the missing nlink is the problem?
Thanks
comment:3 by , 5 years ago
from the given output (fbsd.txt) it is clear that the vboxvfs module in the FreeBSD guest apparently does not provide 'nlink' for directories, it does only provide the link count for files. Also apparently the 'size' information of a directory object is missing as well and is only provided for file objects.
comment:4 by , 5 years ago
Status: | new → awaitsfeedback |
---|
Whatever problem or misbehavior it is that you are trying to show here, using mtree as a vehicle to do that is apparently not going to help.
I did the experiment to check this out using an Ubuntu 18.04.4 host and a Ubuntu 19.04 guest VM, I verified that vboxsf does indeed deliver 'link' counts and 'size' information for file and directory objects. see attached file 'mtree.txt'
https://www.virtualbox.org/attachment/ticket/19430/mtree.txt
Now interestingly we find that although we can prove that vboxsf does provide linkt count and size information, the additionally installed mtree program from the netbsd ports in some strange ways does not display link count and size information for certain file and directory objects.
The conclusion we can draw from this is that whatever problem you have, you need to find another way to reproduce and show it, other then using mtree as mtree is demonstrably unreliable in this regard and may be even buggy.
comment:5 by , 5 years ago
Resolution: | → worksforme |
---|---|
Status: | awaitsfeedback → closed |
closing, please reopen if you have any data and more detailed information.
FreeBSD mtree of directory