Hi Sabuj, Can you give some more information about the dir? how many files are in it.... We have some very larger dir, where ls can take up to 10min. Does "ls -i" work for you? Grtz, Jiri On Apr 15, 2013, at 4:05 PM, Sabuj Pattanayek wrote: > It doesn't look like there's a problem in the actual filesystem since I can go into the directories from the filesystem level and ls works fine. Data looks ok also. > > > On Mon, Apr 15, 2013 at 9:01 AM, Sabuj Pattanayek <sabujp at gmail.com> wrote: > Hi all, > > Anyone ever seen a problem where ls seems to be stuck (can't ctrl+c out, only kill -9), but is actually looping forever in a directory under a simple distributed setup? Seems like inodes have somehow got into a loop? Any suggestions other than running fsck on the underlying filesystems? > > Thanks, > Sabuj > > _______________________________________________ > Gluster-users mailing list > Gluster-users at gluster.org > http://supercolony.gluster.org/mailman/listinfo/gluster-users -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130415/9a1eb1a9/attachment.html>
