Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Use case 1: Currently, the "gluster v quota <volname> list <path>" outputs For eg.., [root@dhcp35-94 test]# gluster v quota vol1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? ------------------------------------------------------------------------------------------------------------------------------- /dir 5.0MB 80% 0Bytes 5.0MB No No Use case 2: Also for "gluster v quota <volname> list-objects <path>" outputs, For eg.., [root@dhcp35-94 test]# gluster v quota vol1 list-objects /dir Path Hard-limit Soft-limit Files Dirs Available Soft-limit exceeded? Hard-limit exceeded? ----------------------------------------------------------------------------------------------------------------------------------------------- /dir 10 80% 0 1 9 No No It would be better if we could display the 80% soft limit equivalent value of the hard limit.
REVIEW: http://review.gluster.org/11808 (quota : display the size of soft limit percentage) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
With the above patch, "gluster v quota <volname> list <path>" command outputs, [root@dhcp35-94 test]# gluster v quota vol1 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? ------------------------------------------------------------------------------------------------------------------------------- /dir 1.0GB 60%(614.4MB) 0Bytes 1.0GB No No "gluster v quota <volname> list-objects <path>" command shows, [root@dhcp35-94 test]# gluster v quota vol1 list-objects /dir Path Hard-limit Soft-limit Files Dirs Available Soft-limit exceeded? Hard-limit exceeded? ----------------------------------------------------------------------------------------------------------------------------------------------- /dir 10 80%(8) 0 1 9 No No
REVIEW: http://review.gluster.org/11808 (quota : display the size of soft limit percentage) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota : display the size of soft limit percentage) posted (#3) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota : display the size of soft limit percentage) posted (#4) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota : display the size of soft limit percentage) posted (#5) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota :display the size of soft limit percentage) posted (#6) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota :display the size of soft limit percentage) posted (#7) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota :display the size of soft limit percentage) posted (#8) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/11808 (quota :display the size of soft limit percentage) posted (#9) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/12337 (cli : freeing the allocated memory) posted (#1) for review on master by Manikandan Selvaganesh (mselvaga)
REVIEW: http://review.gluster.org/12337 (cli : freeing the allocated memory) posted (#2) for review on master by Manikandan Selvaganesh (mselvaga)
COMMIT: http://review.gluster.org/12337 committed in master by Kaushal M (kaushal) ------ commit a2976a2eb8c79cbec1009bec4c420b4874da25bc Author: Manikandan Selvaganesh <mselvaga> Date: Mon Oct 12 15:03:28 2015 +0530 cli : freeing the allocated memory Change-Id: Ibcbad94c091a9c24fe5aff2d7e8bcd9ac88da7bf BUG: 1248521 Signed-off-by: Manikandan Selvaganesh <mselvaga> Reviewed-on: http://review.gluster.org/12337 Tested-by: NetBSD Build System <jenkins.org> Reviewed-by: Vijaikumar Mallikarjuna <vmallika> Reviewed-by: Kaushal M <kaushal>
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