<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Sabuj,<div><br></div><div>Can you give some more information about the dir? how many files are in it....</div><div><br></div><div>We have some very larger dir, where ls can take up to 10min.</div><div>Does "ls -i" work for you?</div><div><br></div><div>Grtz, Jiri</div><div><div><div>On Apr 15, 2013, at 4:05 PM, Sabuj Pattanayek wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">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.<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Apr 15, 2013 at 9:01 AM, Sabuj Pattanayek <span dir="ltr"><<a href="mailto:sabujp@gmail.com" target="_blank">sabujp@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir="ltr">Hi all,<br><br>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?<br>
<br>Thanks,<br>Sabuj <br></div>
</blockquote></div><br></div>
_______________________________________________<br>Gluster-users mailing list<br><a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>http://supercolony.gluster.org/mailman/listinfo/gluster-users</blockquote></div><br></div></body></html>