+++ This bug was initially created as a clone of Bug #1293601 +++ When a quota is disable and enabled again before completing the cleanup operation, this can remove the new xattrs and quota accounting can become wrong Remove removing the xattr, check if quota enabled again and the xattr is new --- Additional comment from Vijay Bellur on 2015-12-22 06:07:42 EST --- REVIEW: http://review.gluster.org/13065 (quota: handle quota xattr removal when quota is enabled again) posted (#1) for review on master by Vijaikumar Mallikarjuna (vmallika) --- Additional comment from Vijay Bellur on 2015-12-22 06:09:48 EST --- REVIEW: http://review.gluster.org/13065 (quota: handle quota xattr removal when quota is enabled again) posted (#2) for review on master by Vijaikumar Mallikarjuna (vmallika) --- Additional comment from Vijay Bellur on 2015-12-28 07:17:28 EST --- REVIEW: http://review.gluster.org/13065 (quota: handle quota xattr removal when quota is enabled again) posted (#3) for review on master by Vijaikumar Mallikarjuna (vmallika)
Patch submitted upstream: http://review.gluster.org/13065
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
Fix "http://review.gluster.org/13065" is available in 3.1.3 as part of rebase
Created 2*2 distributed replicate vol. enabled quota and set limit usage Mount on client and started IO Enabled quota and disabled quota multiple times in loop checked quota list Bug verified on build glusterfs-3.7.9-4.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://access.redhat.com/errata/RHBA-2016:1240