Bug 764901 (GLUSTER-3169) - Memory leak during unlink with quota enabled
Summary: Memory leak during unlink with quota enabled
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-3169
Product: GlusterFS
Classification: Community
Component: quota
Version: mainline
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Junaid
QA Contact:
URL:
Whiteboard:
: GLUSTER-3143 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-14 05:43 UTC by tcp
Modified: 2013-08-06 22:37 UTC (History)
5 users (show)

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

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description tcp 2011-07-14 05:43:08 UTC 
While running the perf tests, it was found that the mainline code causes a memory leak during unlink operations with quota enabled.
The increase in the RSS of the glusterfsd process can be monitored via top(1).
Comment 1 Anand Avati 2011-07-28 05:58:52 UTC 
CHANGE: http://review.gluster.com/73 (Change-Id: I1b01adf1d0ecf494f960d125f2bdcc9c10137115) merged in release-3.2 by Anand Avati (avati)
Comment 2 Anand Avati 2011-07-28 05:59:06 UTC 
CHANGE: http://review.gluster.com/75 (Change-Id: I1b01adf1d0ecf494f960d125f2bdcc9c10137115) merged in master by Anand Avati (avati)
Comment 3 Raghavendra G 2011-08-09 01:23:18 UTC 
*** Bug 3143 has been marked as a duplicate of this bug. ***
Comment 4 Saurabh 2011-08-11 06:43:10 UTC 
executed perf-test.sh on a distribute-replicate, and then took statdump of glusterfsd processes, didn't find any frame leaks

Volume Name: dist-rep
Type: Distributed-Replicate
Status: Started
Number of Bricks: 2 x 2 = 4
Transport-type: tcp
Bricks:
Brick1: 10.1.12.134:/export/d1
Brick2: 10.1.12.135:/export/r1
Brick3: 10.1.12.134:/export/d2
Brick4: 10.1.12.135:/export/r2
Options Reconfigured:
features.limit-usage: /:25GB
features.quota: on

hence moving the bug to resolved state.
Note You need to log in before you can comment on or make changes to this bug.