VirtualBox

Ticket #7004 (reopened defect)

Opened 4 years ago

Last modified 2 years ago

vboxsf attempt to use wildcard with non-existent filenames gives Protocol Error => Fixed in SVN

Reported by: padarjohn Owned by:
Priority: major Component: shared folders
Version: VirtualBox 3.2.4 Keywords: vboxfs
Cc: Guest type: Linux
Host type: Windows

Description

I have a Windows XP host system, with an Ubuntu 10.04 guest OS. I can successfully create and mount a shared folder.

If I try to use wildcards that don't match any files in the folder I get a Protocol Error.

For instance, if the folder has no files that start with the letter 'd', and I try

ls -l d*

I will get

ls: cannot access d*: Protocol error

Not using the wildcard works fine. Using the wildcard with matching files also works fine.

This seems innocuous, but unfortunately it kills the usage of a number of Makefiles in projects with which I'm involved.

Change History

comment:1 Changed 4 years ago by matthijs

Please increase the priority of this problem. I see this problem with Makefiles in VBox 3.2.8 as well.

Thanks!

comment:2 Changed 4 years ago by frank

  • Summary changed from vboxsf attempt to use wildcard with non-existent filenames gives Protocol Error to vboxsf attempt to use wildcard with non-existent filenames gives Protocol Error => Fixed in SVN

Thanks for the report. The fix will be in the next maintenance release (actually in the guest additions).

comment:3 Changed 4 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to fixed

comment:4 Changed 2 years ago by dma_k

  • Status changed from closed to reopened
  • Resolution fixed deleted

I have the same problem. Perhaps this is regression, as I use VirtualBox 4.0.8 r71778:

# ls -l *.o
ls: cannot access *.o: Protocol error
# rm -f *.o
rm: cannot remove `*.o': Protocol error
Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use