If a quota is enabled on a volume and object-limit is set on root directory. Now, if a new brick is added, usage-limit is getting healed on a root directory but object-limit is not healing.
Patch submitted upstream: http://review.gluster.org/#/c/13422/
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/#/c/13422/" available in 3.1.3 as part of rebase
xattr atibutests befote adding brick on replica 0 [root@dhcp46-4 ~]# getfattr -d -m . -e hex /rhs/brick1/b1/ getfattr: Removing leading '/' from absolute path names # file: rhs/brick1/b1/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.dht=0x000000010000000000000000aab565b0 trusted.glusterfs.quota.dirty=0x3000 trusted.glusterfs.quota.limit-objects.1=0x00000000000003e8ffffffffffffffff trusted.glusterfs.quota.limit-set.1=0x0000000280000000ffffffffffffffff trusted.glusterfs.quota.size.1=0x000000000000040000000000000000020000000000000006 trusted.glusterfs.volume-id=0x22b9542504ab40a8b119a19b82778dbf [root@dhcp47-46 ~]# getfattr -d -m . -e hex /rhs/brick1/b2/ getfattr: Removing leading '/' from absolute path names # file: rhs/brick1/b2/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.dht=0x000000010000000000000000aab565b0 trusted.glusterfs.quota.dirty=0x3000 trusted.glusterfs.quota.limit-objects.1=0x00000000000003e8ffffffffffffffff trusted.glusterfs.quota.limit-set.1=0x0000000280000000ffffffffffffffff trusted.glusterfs.quota.size.1=0x000000000000040000000000000000020000000000000006 trusted.glusterfs.volume-id=0x22b9542504ab40a8b119a19b82778dbf xattr atibutests after adding brick on replica 0 [root@dhcp46-4 ~]# getfattr -d -m . -e hex /rhs/brick2/b1/getfattr: Removing leading '/' from absolute path names # file: rhs/brick2/b1/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.quota.limit-objects.1=0x00000000000003e8ffffffffffffffff trusted.glusterfs.quota.limit-set.1=0x0000000280000000ffffffffffffffff trusted.glusterfs.volume-id=0x22b9542504ab40a8b119a19b82778dbf [root@dhcp47-46 ~]# getfattr -d -m . -e hex /rhs/brick2/b2/ getfattr: Removing leading '/' from absolute path names # file: rhs/brick2/b2/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x00000000000000000000000000000001 trusted.glusterfs.quota.limit-objects.1=0x00000000000003e8ffffffffffffffff trusted.glusterfs.quota.limit-set.1=0x0000000280000000ffffffffffffffff trusted.glusterfs.volume-id=0x22b9542504ab40a8b119a19b82778dbf xattr attributes for limit-object are getting healed on newly added brick. Bug verified on build glusterfs-3.7.9-2.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