Bug 762545 (GLUSTER-813) - inode ref leak
Summary: inode ref leak
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-813
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anand Avati
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-08 16:18 UTC by Krishna Srinivas
Modified: 2015-12-01 16:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: RTP
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:


Attachments (Terms of Use)
mem dump (295.07 KB, text/plain)
2010-04-08 14:12 UTC, Krishna Srinivas
no flags Details

Description Krishna Srinivas 2010-04-08 14:12:29 UTC
Created attachment 175 [details]
RH5.x working script

Comment 1 Krishna Srinivas 2010-04-08 16:18:37 UTC
setup: 4 servers, 4 clients, 2 replicates, 1 dht, wb, ra

do this on client:
cp -ar /etc/ /mnt/glusterfs/etc1; echo 3 > /proc/sys/vm/drop_caches;cp -ar /etc/ /mnt/glusterfs/etc1; echo 3 > /proc/sys/vm/drop_caches;cp -ar /etc/ /mnt/glusterfs/etc1; echo 3 > /proc/sys/vm/drop_caches;

do kill -USR1 pid

the dump will show a lot of active inodes - hence inode leak.

Comment 2 Anand Avati 2010-04-08 16:56:58 UTC
PATCH: http://patches.gluster.com/patch/3125 in master (afr: fix inode ref leak in lookup)

Comment 3 Anand Avati 2010-04-08 16:57:16 UTC
PATCH: http://patches.gluster.com/patch/3126 in release-3.0 (afr: fix inode ref leak in lookup)


Note You need to log in before you can comment on or make changes to this bug.