+++ This bug was initially created as a clone of Bug #1065651 +++ Description of problem: After enabling quota command "gluster vol quota dist-vol list" is not displaying quota information. Version-Release number of selected component (if applicable): glusterfs 3.5.0beta3 How reproducible: Everytime Steps to Reproduce: 1.gluster volume quota dist-vol enable 2.gluster volume quota dist-vol limit-usage / 5GB 3.gluster volume quota dist-vol list show 4. Run dd command to client. dd if=/dev/zero of=/mnt/nfs/tes.img bs=1M count=5 Actual results: Path Hard-limit Soft-limit Used Available -------------------------------------------------------------------------------- Expected results: gluster volume quota dist-vol list should quota details. Additional info:
REVIEW: http://review.gluster.org/11738 (quota : checking for absolute path in quota command) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11738 (quota : checking for absolute path in quota command) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
COMMIT: http://review.gluster.org/11738 committed in master by Raghavendra G (rgowdapp) ------ commit 06c3cf61249e05ae1212a43d5fc1db57bad5f718 Author: Manikandan Selvaganesh <mselvaga> Date: Wed Jul 22 15:12:36 2015 +0530 quota : checking for absolute path in quota command Currently, if absolute path is not entered in "gluster volume quota <vol-name> list <path>", it just shows the header (Path Hard-limit Soft-limit...) instead of showing an error message. With this patch, it shows an error to enter the absolute path. Change-Id: I2c3d34bfdc7b924d00b11f8649b73a5069cbc2dc BUG: 1245558 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/11738 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijaikumar Mallikarjuna <vmallika> Reviewed-by: Raghavendra G <rgowdapp>
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