Description of problem: I executed list after setting the limit of 100GB. that does not show the numbers as intended. Version-Release number of selected component (if applicable): glusterfs-server-3.4.0.20rhsquota1-1.el6.x86_64 glusterfs-fuse-3.4.0.20rhsquota1-1.el6.x86_64 glusterfs-3.4.0.20rhsquota1-1.el6.x86_64 How reproducible: happening on this build Steps to Reproduce: 1. create a 6x2 volume, start it 2. enable quota 3. set limit on the root of the volume Actual results: [root@rhsauto032 ~]# gluster volume quota dist-rep list / Path Hard-limit Soft-limit Used Available -------------------------------------------------------------------------------- [root@rhsauto032 ~]# Expected results: the Path should show the path of dir, here it should be "/" the Hard limit should show "100GB" as per this case the Soft-limit should show " the percentage. Used should show the "the amount the space not occupied" Available should show "the amount of space occupied" Additional info:
This works for me. The next time you hit this issue, could you provide the xattrs (and perhaps the logs as well)?
Root Cause for the case described in Comment #3 is the following: The xattr 'trusted.glusterfs.quota.size' is missing in the backend. Therrefore, getxattr on 'trusted.glusterfs.quota.size' fails from the cli (which essentially means that cli does not have the consumed space for displaying in the output of list). Hence the cli displays "N/A" in the 'Used' and 'Available' columns because it truly doesn't have the necessary information available for displaying.
Its a minor regression introduced by http://review.gluster.org/#/c/5615/. Because of this patch no size xattr is set on / till some data is populated. This issue is seen only when brick directory is empty. Still trying to root-cause the issue.
The bug is not in cli and exists because of the absence of trusted.glusterfs.quota.size attribute on the root of the volume after limit is set on it. Hence re-assigning it to Raghavendra G.
https://code.engineering.redhat.com/gerrit/#/c/14140/ is the patch which fixes the issue.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1769.html