When glusterfs is upgraded from 3.6 to 3.7, quota usage can go wrong if inode-quota xattrs are missing
regression test 'tests/bugs/quota/afr-quota-xattr-mdata-heal.t' is failing because of this issue
Did upgrade from 3.0.4 (glusterfs-3.6.0.53-1.el6.x86_64) to glusterfs-3.7.1-10.el6rhs.x86_64 Created 10GB of data Quota list before upgrade [root@node1 yum.repos.d]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 30.0GB 80% 10.0GB 20.0GB No No Create 5GB more data after upgrade Quota list after upgrade to glusterfs-3.7.1-10.el6rhs.x86_64 [root@node2 yum.repos.d]# gluster v quota vol0 list Path Hard-limit Soft-limit Used Available Soft-limit exceeded? Hard-limit exceeded? --------------------------------------------------------------------------------------------------------------------------- / 30.0GB 80% 15.0GB 15.0GB No No Bug verified on build glusterfs-cli-3.7.1-10.el6rhs.x86_64
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html