If there are any quota limit set on a sub-directory. these xattrs are not healed in a newly added brick Steps: 1) Create a volume 2) Enable quota 3) create dir /d1 4) set limit on /d1 5) add new brick 6) send lookup from mount point so that dir /d1 is created on a new brick 7) check 'trusted.glusterfs.quota.limit-set' xattr for /d1 on a new brick There is another issue, where limit xattr not healed on a root directory. This issue is tracked in bug# 1292073
Patch submitted upstream: http://review.gluster.org/#/c/13100/
upstream patch: http://review.gluster.org/#/c/13100/ release-3.7 patch: http://review.gluster.org/13108 downstream patch: https://code.engineering.redhat.com/gerrit/#/c/64638/
*** Bug 1286191 has been marked as a duplicate of this bug. ***
[root@rhs001 /]# gluster v add-brick testvol replica 2 10.70.47.143:/rhs/brick5/b01 10.70.47.145:/rhs/brick5/b02 10.70.47.2:/rhs/brick5/b03 10.70.47.3:/rhs/brick5/b04 volume add-brick: success ========================================================= [root@rhs001 /]# getfattr -d -m. -e hex /rhs/brick5/b01/ .glusterfs/ test/ .trashcan/ [root@rhs001 /]# getfattr -d -m. -e hex /rhs/brick5/b01/test/ getfattr: Removing leading '/' from absolute path names # file: rhs/brick5/b01/test/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x24d8895471c348e89368f48a2c5d377e trusted.glusterfs.dht=0x00000000000000000000000000000000 trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.6=0x000000000000000000000000000000000000000000000001 trusted.glusterfs.quota.limit-set.6=0x0000000080000000ffffffffffffffff trusted.glusterfs.quota.size.6=0x000000000000000000000000000000000000000000000001 ========================================================== [root@rhs002 /]# getfattr -d -m. -e hex /rhs/brick5/b02/ .glusterfs/ test/ .trashcan/ [root@rhs002 /]# getfattr -d -m. -e hex /rhs/brick5/b02/test/ getfattr: Removing leading '/' from absolute path names # file: rhs/brick5/b02/test/ security.selinux=0x73797374656d5f753a6f626a6563745f723a756e6c6162656c65645f743a733000 trusted.gfid=0x24d8895471c348e89368f48a2c5d377e trusted.glusterfs.dht=0x00000000000000000000000000000000 trusted.glusterfs.quota.00000000-0000-0000-0000-000000000001.contri.6=0x000000000000000000000000000000000000000000000001 trusted.glusterfs.quota.limit-set.6=0x0000000080000000ffffffffffffffff trusted.glusterfs.quota.size.6=0x000000000000000000000000000000000000000000000001 Bug verified on build glusterfs-3.7.5-14.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