Bug 1158088 - Quota utilization not correctly reported for dispersed volumes
Summary: Quota utilization not correctly reported for dispersed volumes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: disperse
Version: 3.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Xavi Hernandez
QA Contact:
URL:
Whiteboard:
Depends On: 1158008
Blocks: glusterfs-3.6.2
TreeView+ depends on / blocked
 
Reported: 2014-10-28 14:26 UTC by Xavi Hernandez
Modified: 2015-01-28 14:28 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1158008
Environment:
Last Closed: 2015-01-28 14:28:14 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Xavi Hernandez 2014-10-28 14:26:50 UTC
+++ This bug was initially created as a clone of Bug #1158008 +++

Description of problem:

When quota is enabled on a dispersed volume, the real space usage is not correctly tracked. Quota reports less used space than it's really been used by the files stored on a directory.

Version-Release number of selected component (if applicable): master


How reproducible:

Always

Steps to Reproduce:
1. gluster volume create test disperse server{0..2}:/bricks/test
2. gluster volume start test
3. gluster volume quota test enable
4. gluster volume quota test limit-usage / 1GB
5. mount -t glusterfs server0:/test /gluster/test
6. dd if=/dev/zero of=/gluster/test/file bs=1024k count=512
7. gluster volume quota test list

Actual results:

It reports that there are 256MB used in '/'

Expected results:

It should say that there are 512 MB used if '/'

Additional info:

This is caused by an incorrect accounting of brick contents. Disperse volumes store smaller files on each brick, and only one of these files is used to track disk usage.

A workaround until this bug is solved is to assign a quota smaller than desired to compensate for the incorrect computation. The exact value must be computed this way:

N = Number of bricks of a disperse set
R = Redundancy
Q = Desired quota value
Q' = New quota value

Q' = Q / (N - R)

Then, instead of using:

    gluster volume quota <volname> limit-usage <path> Q

you should use:

    gluster volume quota <volname> limit-usage <path> Q'

When this bug is solved, all quota limits will need to be reverted back to the original value (Q).

--- Additional comment from Niels de Vos on 2014-10-28 13:26:19 CET ---

Marking this as a bug in quota, this should make it pop-up on the radar of the quota developers too.

The final fix may well be in ec-xlator, that is something Xavi can judge.

--- Additional comment from Anand Avati on 2014-10-28 14:02:41 CET ---

REVIEW: http://review.gluster.org/8990 (ec: Correctly handle quota size xattr) posted (#1) for review on master by Xavier Hernandez (xhernandez)

Comment 1 Anand Avati 2014-10-28 14:28:41 UTC
REVIEW: http://review.gluster.org/8992 (ec: Correctly handle quota size xattr) posted (#1) for review on release-3.6 by Xavier Hernandez (xhernandez)

Comment 2 Anand Avati 2014-10-29 16:52:45 UTC
REVIEW: http://review.gluster.org/8992 (ec: Correctly handle quota xattrs) posted (#2) for review on release-3.6 by Xavier Hernandez (xhernandez)

Comment 3 Anand Avati 2014-10-30 08:53:49 UTC
REVIEW: http://review.gluster.org/8992 (ec: Correctly handle quota xattrs) posted (#3) for review on release-3.6 by Xavier Hernandez (xhernandez)

Comment 4 Anand Avati 2014-11-15 18:01:18 UTC
COMMIT: http://review.gluster.org/8992 committed in release-3.6 by Vijay Bellur (vbellur) 
------
commit ab75b15af49a45f0fc7131766cda628e830bec50
Author: Xavier Hernandez <xhernandez>
Date:   Tue Oct 28 14:00:29 2014 +0100

    ec: Correctly handle quota xattrs
    
    This is a backport of http://review.gluster.org/8990/
    
    Change-Id: I35e11d83c318210d44b918e847cf13db35b01510
    BUG: 1158088
    Signed-off-by: Xavier Hernandez <xhernandez>
    Reviewed-on: http://review.gluster.org/8992
    Tested-by: Gluster Build System <jenkins.com>
    Reviewed-by: Dan Lambright <dlambrig>


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