quota-version features is implemented for 3.7.6 please see below patch for more details: http://review.gluster.org/#/c/12386 Problem is when quota is already enabled, we suffix 0 to contri xattr key. This can cause backward compatibility issues when upgraded from 3.7.5 to 3.7.6 and can corrupt accounting information
upstream patch: http://review.gluster.org/#/c/12660 release-3.7 patch: http://review.gluster.org/#/c/12661/
downstream patch: https://code.engineering.redhat.com/gerrit/#/c/62064/
Installed build glusterfs-3.7.5-5.el7rhgs.x86_64 . Created volume , enabled quota and limit-usage. Created some data. Checked quota list. Updated system to build glusterfs-3.7.5-11.el7rhgs.x86_64. Quota list displayed soft and hard limit same as before upgrade. Hence marking this bug verified on build glusterfs-3.7.5-11.el7rhgs.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/RHBA-2016-0193.html