Red Hat Bugzilla – Bug 1064265
quota: allowed to set soft-limit %age beyond 100%
Last modified: 2016-09-20 00:29:25 EDT
Description of problem: allowed to set the soft-limit percentage more than 100% Version-Release number of selected component (if applicable): glusterfs-3.4.0.59rhs-1.el6rhs.x86_64 How reproducible: always Steps to Reproduce: 1. create a volume, start it 2. enable quota 3. mount over nf 4. create a directory inside the mount point 5. gluster volume quota limit-usage /dir-name <size> <soft-limit-percentage> define soft-limit percentage as 100% Actual results: step5 result, [root@quota6 ~]# gluster vol quota dist-rep2 limit-usage /dir8 5GB 650% volume quota : success Expected results: should not cross 100% Additional info:
Patch posted upstream for review http://review.gluster.org/#/c/11566/
Patch merged upstream.
*** Bug 1253224 has been marked as a duplicate of this bug. ***
https://code.engineering.redhat.com/gerrit/#/c/55071/1
*** Bug 1253222 has been marked as a duplicate of this bug. ***
[root@darkknight ~]# gluster v quota testvol limit-usage /test 50GB 100% volume quota : success [root@darkknight ~]# gluster v quota testvol list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 100.0GB 80% 0Bytes 100.0GB No No /test 50.0GB 100% 0Bytes 50.0GB No No [root@darkknight ~]# gluster v quota testvol limit-usage /test 50GB 101% Please enter a correct value in the range of 0 to 100 Usage: volume quota <VOLNAME> {enable|disable|list [<path> ...]| list-objects [<path> ...] | remove <path>| remove-objects <path> | default-soft-limit <percent>} | volume quota <VOLNAME> {limit-usage <path> <size> [<percent>]} | volume quota <VOLNAME> {limit-objects <path> <number> [<percent>]} | volume quota <VOLNAME> {alert-time|soft-timeout|hard-timeout} {<time>} Bug verified on glusterfs-3.7.1-12.el7rhgs.x86_64
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-1845.html