Description of problem: ======================= With the new changes in quota, heal doesn't work from client to reflect the 128bit attribute changes. listing the quota on an upgraded volume gives N/A for all the fields. While the same works for new volume. [root@rhs3 opt]# gluster v quota newvol list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / N/A N/A N/A N/A N/A N/A [root@rhs3 opt]# gluster v quota newvol limit-usage / 1GB volume quota : success [root@rhs3 opt]# gluster v quota newvol list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / N/A N/A N/A N/A N/A N/A [root@rhs3 opt]# Version-Release number of selected component (if applicable): ============================================================= [root@rhs3 opt]# gluster --version glusterfs 3.7dev built on Mar 28 2015 01:05:28 Repository revision: git://git.gluster.com/glusterfs.git Copyright (c) 2006-2011 Gluster Inc. <http://www.gluster.com> GlusterFS comes with ABSOLUTELY NO WARRANTY. You may redistribute copies of GlusterFS under the terms of the GNU General Public License. [root@rhs3 opt]# How reproducible: ================= 100% Actual results: N/A for all the fields displayed Expected results: Should reflect the appropriate values Additional info: ================ Sosreports will be attached.
Created attachment 1009499 [details] SOSREPORT
Its a disperse volume. We need to handle quota xattr aggregation for disperse, ec and sharding volumes.
REVIEW: http://review.gluster.org/10112 (quota/disperse: handle inode quotas in xattr aggregate) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10112 (quota/disperse: handle inode quotas in xattr aggregate) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10112 (quota/disperse: handle inode quotas in xattr aggregate) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/10112 committed in master by Raghavendra G (rgowdapp) ------ commit 6e8298654a7d0de29192b88d769132cfc51c9ac7 Author: vmallika <vmallika> Date: Wed Apr 1 20:03:37 2015 +0530 quota/disperse: handle inode quotas in xattr aggregate with the inode quota feature, quota size is now increased from 64bit to 192bits which contains values of 'file size', 'file count' and 'dir count' This change in quota size xattr needs to be handled in disperse xattr aggregation Signed-off-by: vmallika <vmallika> Change-Id: I5fd28aa9f5b8b6cba83a98360236417a97ac16ee BUG: 1207967 Reviewed-on: http://review.gluster.org/10112 Reviewed-by: Pranith Kumar Karampuri <pkarampu> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Sachin Pandit <spandit> Reviewed-by: Raghavendra G <rgowdapp> Tested-by: Raghavendra G <rgowdapp>
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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user