I searched the forum for virtualbox but did not found anything.
I have a Host running Windows 7, and a guest running Windows XP. I share a folder (NTFS) from host to guest, using the shared folders schema of virtualbox. The shared folder is mounted in virtualbox as a network share via \\virtualsrv\foldername (Q:\folderpath\foldername) Folder in host has granted all permissions to all ... shared with full permissions.
Using latest vbox with latest extensions and latest guest additions ... W 7 and W XP 100% updated ...
I can copy files with explorer, move, etc without any problem manually from C: to Q: ...
I try to sync a local guest folder (c:\localfolder) (FAT32) with the shared Q:\folderpath\foldername
When asked to compare I receive:
Cannot set directory to lock for Q:\folderpath\foldername
Cannot write file Q:\folderpath\foldername\sync.ffs_lock
After ignoring, comparison gives 0 disimilarities (folders where equal)
Then I try to compare C:\localfolder with Q:\folderpath\foldername\EMPTYTEST
I receive a warning (non existing folder) order go ahead, and 243 files are copied.
Now, a comparison between C:\localfolder with Q:\folderpath\foldername\EMPTYTEST
produces a new message
Cannot set directory to lock for Q:\folderpath\foldername\EMPTYTEST
Cannot write file Q:\folderpath\foldername\EMPTYTEST\sync.ffs_lock
Error Code 5: denied access ... ignoring produces cero diffs (as it should)
WTF?
TIA
Ctone
Help with virtualbox shared folders
- Posts: 2
- Joined: 16 Nov 2004
- Site Admin
- Posts: 7281
- Joined: 9 Dec 2007
Thanks for the report! There seems to be a problem with the Virtual Box network drivers not being able to update a hidden file (the sync.ffs_lock), although the CreateFile call correctly passes the hidden file attributes. Anyway, FFS does not really require the lock file to be hidden, so here's the fixed version:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.16_beta_Windows_Setup.exe]
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.16_beta_Windows_Setup.exe]
- Posts: 2
- Joined: 16 Nov 2004
Guau! so fast!Thanks for the report! There seems to be a problem with the Virtual Box network drivers not being able to update a hidden file (the sync.ffs_lock), although the CreateFile call correctly passes the hidden file attributes. Anyway, FFS does not really require the lock file to be hidden, so here's the fixed version:
[404, Invalid URL: http://freefilesync.sourceforge.net/FreeFileSync_5.16_beta_Windows_Setup.exe]Zenju
I am on leave for a week, will report when back
Thanks again
CTone