On Tue, May 1, 2012 at 1:59 PM, Camelia Botez <camelia.bo...@weizmann.ac.il>wrote:
> I have 2 servers running Rhel5 and Centos5.**** > > Around 2 weeks ago on both of them , I have specific directories on which > ls command gets stuck.**** > > I don’t get any output from ls , I cannot stop the command – I only can > close the window.**** > > I rebooted the servers and when I saw that reboot didn’t help I ran > manually fsck.**** > > No improvement.**** > > Has anyone any idea what can be the cause and what to do?**** > > > > > Things I can think of... Anything on dmesg when this happens? Did you verify that those directories are indeed on the volume you fsck'd ? (and not a network share, etc.) Are those 'stock' directories (part of the install) or something you've added? If stock, what's the path? (to know if it's a special one, augmenting the previous question) Is the problem with actual listing, or 'ls' itself? Did you try, for example, cat /path/to/dir/ <tab> <tab> to see if the shell does manage to read the directory contents? Do the stuck process get into D state (in 'ps axuf') like I assume it is? I know I didn't answer the question but maybe an answer to one of these questions might :) That's it for now... -- Shimi
_______________________________________________ Linux-il mailing list Linux-il@cs.huji.ac.il http://mailman.cs.huji.ac.il/mailman/listinfo/linux-il
