Bug 1419431

Summary: Stale gfid in quota.conf should be cleaned up.
Product: [Community] GlusterFS Reporter: Sanoj Unnikrishnan <sunnikri>
Component: quotaAssignee: Sanoj Unnikrishnan <sunnikri>
Status: CLOSED WONTFIX QA Contact: Vinayak Papnoi <vpapnoi>
Severity: medium Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, vpapnoi
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-03-09 18:18:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sanoj Unnikrishnan 2017-02-06 06:49:17 UTC 
Description:
For a directory with quota limit set, if an rmdir is done without prior remove limit on the path, the gfid corresponding to the dir remains in quota.conf.

This causes the quota.conf to grow. Each gfid entry takes 17 bytes (16:gfid, 1:type). So it grows very slowly.

Another issue that stale gfid causes is that it increases ipc calls to quotad during list (one per gfid).

Proposed solution:
Since very few dirs would have limit set on them, it may be an overkill to handle these during rmdir. Instead we could clean them during quota list operation.