When a quota limit is not set, 'quota list <path>' should still display the usage when a path parameter is specified. # gluster volume quota vol1 list / quota: No quota configured on volume vol1 # g;uster volume quota vol1 list-objects / quota: No inode quota configured on volume vol1 We have specified a path '/' in quota list command and we are getting error 'No quota configured' Expected result: # gluster volume quota vol1 list-objects / Path Hard-limit Soft-limit Files Dirs Available Soft-limit exceeded? Hard-limit exceeded? ----------------------------------------------------------------------------------------------------------------------------------------------- / N/A N/A 1 3 N/A N/A N/A # gluster volume quota vol1 list / Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? ------------------------------------------------------------------------------------------------------------------------------- / N/A N/A 1.0MB N/A N/A N/A
Here is the test-case: 1) create volume 2) enable quota, but do not set any limits 3) create some files 4) execute quota list with path specified at the end #gluster volume quota vol1 list / #gluster volume quota vol1 list-objects /
REVIEW: http://review.gluster.org/13893 (quota/cli: display quota usage on path when limit not set) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/13893 committed in master by Vijaikumar Mallikarjuna (vmallika) ------ commit b198cdd6a47a964a102e8e96dc0de34cd19c2fd5 Author: vmallika <vmallika> Date: Sat Apr 2 09:20:45 2016 +0530 quota/cli: display quota usage on path when limit not set When a quota limit is not set, 'quota list <path>' should still display the usage when a path parameter is specified. Change-Id: Ida12d9c5e348fbd98db4d68d9324c623cbdd3dea BUG: 1323360 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/13893 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Manikandan Selvaganesh <mselvaga> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp> Smoke: Gluster Build System <jenkins.com>
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