[Bugs] [Bug 1353855] Possible memory leak in the glusterfs client after upgrade to RHGS 3.1.2

[bugzilla at redhat.com]

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

Raghavendra G <rgowdapp at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
           Assignee|bugs at gluster.org            |rgowdapp at redhat.com



--- Comment #1 from Raghavendra G <rgowdapp at redhat.com> ---
--- Additional comment from Raghavendra G on 2016-07-08 01:58:08 EDT ---

Seems like there is a leak in inodes:

# grep fuse.itable.active glusterdump.2460.dump.1467123831 | tail -1

[xlator.mount.fuse.itable.active.2904698]

As can be seen above there are 2904698 "active" inodes, which strongly points
towards a leak.

regards,
Raghavendra

--- Additional comment from Raghavendra G on 2016-07-08 02:30:54 EDT ---

[raghu at unused 1353774]$ grep ia_type=1 ./glusterdump.2460.dump.1467123831 | wc
-l
3457676
[raghu at unused 1353774]$ grep ia_type=2 ./glusterdump.2460.dump.1467123831 | wc
-l
637

Seems like most of the inodes that leaked are regular files.

--- Additional comment from Raghavendra G on 2016-07-08 04:44:31 EDT ---

I think leak was introduced by http://review.gluster.org/#/c/11892/
for inodes on which "need-lookup" is set (typically the ones returned by
readdirp), we call entry resolution even though loc->inode is set (as inode was
already present in itable). However, fuse_resolve_entry_cbk assumes loc->inode
is unset always, thereby overriding loc->inode with a new value without doing
an unref.

regards,
Raghavendra

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.