Description of problem: Currently afr_fsync() is not a transaction and will not guarantee data durability at the moment. Make it a transaction to achieve this. 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/19621 (cluster/afr: Make afr_fsync a transaction) posted (#1) for review on master by Karthik U S
COMMIT: https://review.gluster.org/19621 committed in master by "Pranith Kumar Karampuri" <pkarampu> with a commit message- cluster/afr: Make afr_fsync a transaction Change-Id: I713401feb96393f668efb074f2d5b870d19e6fda BUG: 1548361 Signed-off-by: karthik-us <ksubrahm>
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-v4.1.0, please open a new bug report. glusterfs-v4.1.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] http://lists.gluster.org/pipermail/announce/2018-June/000102.html [2] https://www.gluster.org/pipermail/gluster-users/