+++ This bug was initially created as a clone of Bug #1064265 +++ 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:
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage.) posted (#4) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage.) posted (#5) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage) posted (#6) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage) posted (#7) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11566 (quota : validating soft limit percentage.) posted (#8) for review on master by Manikandan Selvaganesh (mselvaga)
Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well.
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.0, please open a new bug report. glusterfs-3.8.0 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user