Page 1 of 1
Shared Folder "protocol error" when rm files or us
Posted: 17. Dec 2008, 19:10
by ggeisen
Share folder is mounted rw and I can browse, create and delete files, but some operations fail with a "protocol error". Specifically the commands `rm ~*`, `rm *.o` and `ar <library>`.
WinVista host with folder shared (all firewalls off)
RedHat 7, CentOS, Ubuntu guests (all exhibit same problem)
Posted: 18. Dec 2008, 00:34
by Sasquatch
Do you get the same error if you do it from a file manager like Nautilus? If you want to remove a file that starts with a tilde (~), you need to tell it that it's the current folder, as ~ is also referred to your home folder.
Posted: 18. Dec 2008, 22:29
by ggeisen
`rm *.o` fails also, as root
interesting though ... if no .o files exist I get the error (which I can probably live with) but `rm *.o` works silently if at least one .o file exists.
Now I just have to figure out what's going on with the `ar` command
Re: Shared Folder "protocol error" when rm files or us
Posted: 9. May 2010, 22:22
by ile
I get a lot of these when compiling stuff.
Re: Shared Folder "protocol error" when rm files or us
Posted: 9. May 2010, 23:46
by Sasquatch
Did you check the small FAQ in my Shared Folders guide (
Howto: Use Shared Folders)? If that doesn't work, then it appears that shared folders isn't really made for compiling source code. I've read other replies of Windows users unable to run their Visual Studio projects from a shared folder. I know it is an additional step in compiling software, but copy the sources to the local drive of the VM and compile it from there.
Re: Shared Folder "protocol error" when rm files or us
Posted: 10. May 2010, 00:48
by ile
Yes, I did. I have a Win7 host and a Linux guest, and get these "rm: protocol errors", also there was some other problems with compiling, but the cause may be similar as for the protocol errors.
Well, I will try a FAT32 filesystem next for the shared folder id it makes any difference...
Re: Shared Folder "protocol error" when rm files or us
Posted: 10. May 2010, 21:55
by Sasquatch
It's not the Host file system that's the problem, it's either the shared folder name and mount point on the Linux Guest. With copying it to a local drive, I mean you copy the files you want to compile to the VM drive itself. I'm sure that it will compile properly after that.
Re: Shared Folder "protocol error" when rm files or us
Posted: 11. May 2010, 06:50
by ile
Yes, I'm sure copying will work, but that would defeat some benefits of the shared folder - I would like to use editor in Windows and compile in Linux...
Re: Shared Folder "protocol error" when rm files or us
Posted: 21. Nov 2010, 15:33
by marriealen
These errors are mainly due to locked long paths,to do it efficiently i had used a tool available at
http://pathtoodeep.com ,it will surely help you resolve this problem