Hi all, I have a Linux Fedora Core 10 installed in a Parallels 4 VM with my Mac home folder shared with the VM. Everything seems to work well, I can browse the directories in the shared folder without problem… except a few ones. For these ones, if I go in a Linux terminal and do a 'ls' on them, the command just never returns (or takes so long to return I've given up each time). The strange thing is that there's nothing special with these directories. There are dozens of other ones with the same kind of name, owner, permissions, and so on… But these particular ones are just impossible to browse, freezing the commands. Has anyone seen this kind of problem before? Any idea about the cause? Any way to solve it? Did a search on these forums and a Google search, but didn't find any information on what might happen. Thanks in advance. - Eric -
Doesn't anyone have any hint on this? This is becoming really annoying: It happens with Debian 5.0 as well as with Fedora Core 10. I tried to change the mount options, listing as another user, and quite a few other things. Nothing works. The freeze happens with 'ls' in a terminal as well as with any file browser. I tried to find any clue on which shared folders cause the problem, but didn't find any; Seems to be random, but consistent: If I restart the virtual machine, the problem is still there on the very same folders. When reproducing the problem with 'ls' in a terminal, I always end up having to interrupt the 'ls' command with Ctrl+C. If it works, it always prints one of the file names in the folder just before quitting. What can be the problem here? - Eric -
Replying to myself again: I did some more investigation and the folders that cause the problem always seem to have quite a large number of files in them, like more than 300 or 400… I could even reproduce the problem by doing the following: - On the Mac, I create an empty folder; - In this folder, I create like 500 empty files; - In the VM, I open a terminal, cd to the shared folder above and do a 'ls' -> freeze. I have to interrupt the command with Ctrl-C… Can anybody reproduce that? Thanks. - Eric -
Anybody? Can anybody please test the scenario I gave above and tell me if it works or not? I'd like to know if the problem is with my configuration or if it's actually a bug before reporting it to Parallels. Here is a shell script that creates 600 empty files on the Mac: ----- mkdir foo cd foo for i in 0 1 2 3 4 5 do for j in 0 1 2 3 4 5 6 7 8 9 do for k in 0 1 2 3 4 5 6 7 8 9 do touch file$i$j$k.txt done done done ----- Can anyone please run it on a Mac (in the Terminal application, in directory ~/Documents for example), then go in the Linux VM and try to list the directory contents (ls /media/psf/Home/Documents/foo) and tell me if they experience the same freeze? Thanks a lot in advance. - Eric -
