[Bugs] [Bug 1158088] New: Quota utilization not correctly reported for dispersed volumes

[bugzilla at redhat.com]

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

            Bug ID: 1158088
           Summary: Quota utilization not correctly reported for dispersed
                    volumes
           Product: GlusterFS
           Version: 3.6.0
         Component: quota
          Assignee: bugs at gluster.org
          Reporter: xhernandez at datalab.es
                CC: bugs at gluster.org, gluster-bugs at redhat.com,
                    ndevos at redhat.com



+++ 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 at datalab.es)

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