[Gluster-users] ls seems to be stuck, but keeps looping in a directory in a distributed setup
j.hoogeveen at bluebillywig.com
Mon Apr 15 14:09:34 UTC 2013
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?
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?
> Gluster-users mailing list
> Gluster-users at gluster.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Gluster-users