Description of problem: When a file is renamed it is updating the read_subcols in the inode_ctx of the file. Since rename does not change any data in the file, we should not update the read_subvols after the rename. Updating it, can lead to serving stale data for the immediate reads. 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/21841 (cluster/afr: Do not update read_subvol in inode_ctx after rename) posted (#1) for review on master by Karthik U S
REVIEW: https://review.gluster.org/21841 (cluster/afr: Do not update read_subvol in inode_ctx after rename/link fop) posted (#4) for review on master by Karthik U S
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-6.0, please open a new bug report. glusterfs-6.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/2019-March/000120.html [2] https://www.gluster.org/pipermail/gluster-users/