Description of problem:
The "trusted.glusterfs.mdata" xattr was present on a dir on brick1 when it was created, but when added new brick (brick2) to the volume, and did rebalance as well, the xattr was not present on the dir on new brick(brick2).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Create a 1 brick distributed volume.
2.Mount the volume on a client node using fuse.
3.Create a dir on client node
4.Check all the internal xattrs for the dir1 on the back-end using:
#getfattr -de hex -m . /bricks/brick1/dir1
5.Add a new brick to the volume.
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.