There is a problem during upgrade where, inode quotas are not healed in the contri xattrs. Healing happens if conri xattrs are missing but doesn't happen if contri xattrs are present, but inode quota values are missing in the contri xattrs.
REVIEW: http://review.gluster.org/10239 (quota/marker: fix inode quota healing after glusterfs upgrade) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika)
REVIEW: http://review.gluster.org/10239 (quota/marker: fix inode quota healing after glusterfs upgrade) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika)
COMMIT: http://review.gluster.org/10239 committed in master by Raghavendra G (rgowdapp) ------ commit 50b9dd3559802160aea923945fc104824fc76064 Author: vmallika <vmallika> Date: Wed Apr 15 05:50:01 2015 +0530 quota/marker: fix inode quota healing after glusterfs upgrade There is a problem during upgrade where, inode quotas are not healed in the contri xattrs. Healing happens if contri xattrs are missing. But healing doesn't happen if contri xattrs are present and inode quota values are missing in the contri xattrs. This patch fixes the problem Change-Id: I6c88b74b5bb333a97c5419e24cc4ada82839f474 BUG: 1211808 Signed-off-by: vmallika <vmallika> Reviewed-on: http://review.gluster.org/10239 Tested-by: NetBSD Build System Reviewed-by: Sachin Pandit <spandit> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Raghavendra G <rgowdapp> Tested-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