From: Frédéric L. W. M. <lis...@pe...> - 2009-11-12 03:13:24
|
Using 2.6.25.20 or 2.6.26.8, updatedb (here, mlocate) sometimes hangs coLinux. I guess it has to do with cofs, because it also scans the Windows partitions. When I used ^C to kill the VM, the following appeared. fuse_dir_open: host returned error: ffffffff fuse_dir_open: host returned error: ffffffff colinux: Linux VM terminated colinux: powered off, exiting. Here, updatedb runs daily at 1:00. |
From: Henry N. <hen...@ar...> - 2009-11-12 20:29:23
|
Am 12.11.2009 04:12, schrieb Frédéric L. W. Meunier: > Using 2.6.25.20 or 2.6.26.8, updatedb (here, mlocate) sometimes > hangs coLinux. I guess it has to do with cofs, because it also > scans the Windows partitions. When I used ^C to kill the VM, the > following appeared. > > fuse_dir_open: host returned error: ffffffff > fuse_dir_open: host returned error: ffffffff > There errors comes from trying to entering a directory without permission. Try to simulate the "updatedb" by running such command: cd /windows find . -name 'Nothing, just scanning all dirs' If that also stops, then go one directory level deeper and try the same. Do this again with all directories from top most. ("System Volume Information", C:\Winows, C:\Programm, ...) If you found the hanging directory, then change into the failed directoy and do run the check for every singe directory there again, ... Up to have the problematic file or directoy. Than we can see how we can skip it. -- Henry N. |