This is part of bug 763990. We have to make sure all the data/meta-data related to a file are properly migrated when a file gets migrated as part of rebalance. Currently I did tests to check if the extended attributes (anything other than glusterfs's xattrs) are not getting copied over to destination.
*** Bug 3099 has been marked as a duplicate of this bug. ***
PATCH: http://patches.gluster.com/patch/7825 in release-3.2 (glusterd rebalance: bring in feature to migrate extended attributes too)
PATCH: http://patches.gluster.com/patch/7840 in release-3.2 (glusterd rebalance: mount with '--acl' option for rebalancing.)
CHANGE: http://review.gluster.com/9 (currently when a file gets migrated, the extended attributes of the) merged in release-3.1 by Anand Avati (avati)
tested with 3.1.6qa3. 1.set custom extended attribute using setfattr on 25 files. 2.Added 2 more brick (/export3) to existing dht-afr(/export1,export2) volume. 3.now did a rebalance. 4.user given extended attributes are present on new bricks(export3) getfattr -d -m . /export3/24.txt getfattr: Removing leading '/' from absolute path names # file: export3/24.txt trusted.gfid=0syhDrGQ97RluQC+4W/MyCTQ== trusted.user.foo="bar"