Date: Tue, 24 Mar 2020 23:26:55 -0400 From: Nicholas Papadonis <nick.papadonis.ml@gmail.com> To: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Cc: Mario Lobo <lobo@bsd.com.br>, Manish Jain <bourne.identity@hotmail.com> Subject: Re: vboxvfs file integrity problems? Message-ID: <CC6E6ECF-4C61-4644-89DA-1B76B2722C8F@gmail.com> In-Reply-To: <E3C7BBDE-C36D-4418-BFC3-7E95B042F4BD@gmail.com> References: <CAKD0t1KrEhPG4--2f9J%2BcSVXdDp_JNv7Ztv0PG1eHdPC-NuUKg@mail.gmail.com> <CAKD0t1JEuNrzhsW5gx5Sz0Yrq_qnuPo_Dvz10SjJV7mQa7zAjQ@mail.gmail.com> <CA%2ByoEx_2dmMm1wf95s1ydfTQ5iCN9sH=akQYq5B1V=EdM7MtFA@mail.gmail.com> <A1BE9EBA-84EC-4C34-B2CB-3683CC5432AD@gmail.com> <DB8PR06MB6442DE184E5FF9E1E13C65AEF6F00@DB8PR06MB6442.eurprd06.prod.outlook.com> <DB8PR06MB64423F4FC86207DFA0B53EA3F6F00@DB8PR06MB6442.eurprd06.prod.outlook.com> <0438AA11-06BB-4D8B-BDF9-8F15E785882D@gmail.com> <27A6356A-AC35-4526-898B-88C87FAC703B@gmail.com> <E3C7BBDE-C36D-4418-BFC3-7E95B042F4BD@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 =E2=80=9Cnlink=3DX=E2=80=9D field. = size is also missing, but I=E2=80=99m assuming that=E2=80=99s expected = as it=E2=80=99s missing on the nfs mount as well. $ diff mtreenfs-mount.txt mtreeonmac.txt|more < branches type=3Ddir nlink=3D2 time=3D1547439167.000000000 --- > branches type=3Ddir nlink=3D2 size=3D64 = time=3D1547439167.000000000 diff mtreenfs-mount.txt mtree-fbsd-vboxvfs.txt |less < branches type=3Ddir nlink=3D2 time=3D1547439167.000000000 --- > branches type=3Ddir time=3D1547439167.000000000 Perhaps the missing nlink is the problem? Thanks > On Mar 24, 2020, at 1:05 PM, Nicholas Papadonis = <nick.papadonis.ml@gmail.com> wrote: >=20 > vboxvfs works to mount the directory. I can read and write files, = however I=E2=80=99m observing integrity issues of the mount point. >=20 > Does anyone know of an application to test file integrity over the = mount? >=20 > Files in the mount subpath that are accessible from the host and = Debian are not accessible in FreeBSD via vboxvfs. Oddly, command line = completion will show the directory, however the directory is missing = from =E2=80=98ls -l=E2=80=99. Appreciate any guidance on how to test = the integrity of vboxvfs. >=20 > Thanks >=20 >=20 >> On Mar 24, 2020, at 12:34 PM, Nicholas Papadonis = <nick.papadonis.ml@gmail.com> wrote: >>=20 >> Solved. >>=20 >> /etc/fstab: >> Source /mnt/srcr vboxvfs rw,uid=3D1001 0 = 0 >>=20 >>> On Mar 24, 2020, at 12:12 PM, Nicholas Papadonis = <nick.papadonis.ml@gmail.com> wrote: >>>=20 >>> I updated to the latest and it works! >>>=20 >>> $ sudo mount -t vboxvfs -o uid=3D1001 Source /mnt/srcr >>>=20 >>> $ uname -a >>> FreeBSD fbsd 12.1-RELEASE FreeBSD 12.1-RELEASE r354233 GENERIC = amd64 >>>=20 >>> The only issue is the mount points are not made permanent according = to the Shared Folders dialog in VirtualBox. >>>=20 >>> I tried editing fstab, however the changes were lost. Does anyone = know where to place the mount options? >>>=20 >>> Thanks >>>=20 >>>> On Mar 23, 2020, at 7:33 PM, Manish Jain = <bourne.identity@hotmail.com> wrote: >>>>=20 >>>> Another correction : the type should not be vboxvfs, rather vboxsf = : >>>>=20 >>>> sudo mount -t vboxsf -o uid=3D1000 Source /mnt/srcr >>>>=20 >>>>=20 >>>> On 24/03/2020 04:54, Manish Jain wrote: >>>>> On 24/03/2020 03:42, Nicholas Papadonis wrote: >>>>>> sudo mount -t vboxvfs Source /mnt/srcr >>>>> I think that command is wrong. Try: >>>>> sudo mount -t vboxvfs -o uid=3D1000 Source /mnt/srcr >>>>> (Presuming your non-root user is UID 1000) >>>>> Regards, >>>>> Manish Jain >>>=20 >>=20 >=20
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CC6E6ECF-4C61-4644-89DA-1B76B2722C8F>