Description of problem: The quota limit used to setting the quota on any directory. This time I used it to set the limit of 16384PB and subsequently used the "quota list" command to collect stats related to quota. Found it out that it said "Soft-limit exceeded and Hard-limit exceeded" is said to be "Yes" whereas it should be "No" Version-Release number of selected component (if applicable): glusterfs-3.6.0.11-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. create a 6x2 volume, start it 2. enable quota 3. set quota limit of 16384PB 4. execute the quota list command Actual results: the quota list result, [root@nfs1 ~]# gluster volume quota dist-rep1 limit-usage / 16384PB volume quota : success [root@nfs1 ~]# [root@nfs1 ~]# [root@nfs1 ~]# [root@nfs1 ~]# gluster volume quota dist-rep1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 0Bytes 80% 0Bytes 0Bytes Yes Yes Expected results: it should say Hard-limit set as 16384B and "No" "No" for Soft-limit exceeded? and Hard-limit exceeded? Additional info:
Patch submitted upstream: http://review.gluster.org/#/c/10022/
[root@darkknight ~]# gluster v quota vol0 limit-usage / 16386PB volume quota : success [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 2.0PB 80% 0Bytes 2.0PB No No [root@darkknight ~]# gluster v quota vol0 limit-usage / 9223372036854775807 volume quota : success [root@darkknight ~]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 8192.0PB 80% 0Bytes 8192.0PB No No Bugs successfully verified on build glusterfs 3.7.0 . Hence marking this bug as verified.
Hi Vijai, The doc text is updated. Please review the same and share your technical review comments. If it looks ok, then sign-off on the same. Regards, Bhavana
Doc-Text looks good to me
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. https://rhn.redhat.com/errata/RHSA-2015-1495.html