In a heterogeneous cluster with op_version less 3.7, quota inodes will account on those bricks which has glusterfs version 3.7 and no this is not available in older version. This will have incorrect values displayed when user queries inode count from CLI. So CLI should display error 'Inode quotas supported only with cluster version 3.7 and above'
REVIEW: http://review.gluster.org/10261 (quota: display error when setting/removing object limits with ver < 3.7) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10261 (quota: display error when inode-quota cmds executed with cluster ver < 3.7) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10261 (quota: display error when inode-quota cmds executed with cluster ver < 3.7) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10261 (quota: display error when inode-quota cmds executed with cluster ver < 3.7) posted (#4) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10261 (quota: display error when inode-quota cmds executed with cluster ver < 3.7) posted (#5) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/10261 committed in master by Vijay Bellur (vbellur) ------ commit 1adf231fc425ac35eb91a5b771ea0c5c97b1f6c3 Author: vmallika <vmallika> Date: Thu Apr 16 08:10:01 2015 +0530 quota: display error when inode-quota cmds executed with cluster ver < 3.7 In a heterogeneous cluster with op_version less than 3.7, inode quotas will be accounted on those bricks which has glusterfs version 3.7 and this is not available in older version. This will have incorrect values displayed when user queries inode count from CLI. This patch will display error when inode-quota commands are executed with cluster version less than 3.7 Change-Id: Ia0e6d5635d1d8e7b2e2cfc3daa7b7f9e314a263a BUG: 1212253 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/10261 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Vijay Bellur <vbellur>
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