Description of problem:
To avoid incorrectness of user xattr at backend leverage MDS subvol for dht_removexattr.
After introducing MDS(from patch https://review.gluster.org/#/c/15468/) to heal custom xattrs we can use the same MDS for remove custom xattr also.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
REVIEW: https://review.gluster.org/19971 (cluster/dht: Leverage MDS subvol for dht_removexattr also) posted (#1) for review on master by MOHIT AGRAWAL
COMMIT: https://review.gluster.org/19971 committed in master by "Amar Tumballi" <email@example.com> with a commit message- cluster/dht: Leverage MDS subvol for dht_removexattr also
Problem: In a distributed volume situation can be arise when custom
extended attributed are not removed from all bricks after
stop/start or added newly brick.
Solution: To resolve the same use MDS subvol for remove xattr also
Signed-off-by: Mohit Agrawal <firstname.lastname@example.org>
This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.0, please open a new bug report.
glusterfs-5.0 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.