[Bugs] [Bug 1344885] inode leak in brick process

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1344885

Mohamed Ashiq <mliyazud at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mliyazud at redhat.com



--- Comment #8 from Mohamed Ashiq <mliyazud at redhat.com> ---
Hi,

I did some more test with respect to inode-leak in bricks. I have attached the
statedump and fusedump. Here is what I did:

created a 2x2 volume

mounted with fuse dump option enabled
# glusterfs --volfile-server=<IP ADDR> --dump-fuse=/home/dump.fdump
--volfile-id=/vol /mnt/mount

# cd /mnt/mount

# for i in {1..50}; do mkdir healthy$i; cd healthy$i; echo dsfdsafsadfsad >>
healthy$i; cd ../; done

# find .

# rm -rf ./*

# gluster volume statedump vol

# for i in {1..50}; do mkdir healthy$i; cd healthy$i; done

# cd /mnt/mount

# find .

# rm -rf ./*

# gluster volume statedump vol

brick/4 has inode leaks when creating directories on mount recursively and not
on samelevel.

fusedump is took and parsed with https://github.com/csabahenk/parsefuse to make
it human readable. fusedumps are attached.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=UPDgjQa9Cr&a=cc_unsubscribe