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): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
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" <amarts> 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 BUG: 1575587 Change-Id: I7701e0d3833e3064274cb269f26061bff9b71f50 fixes: bz#1575587 Signed-off-by: Mohit Agrawal <moagrawa>
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 [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://lists.gluster.org/pipermail/announce/2018-October/000115.html [2] https://www.gluster.org/pipermail/gluster-users/