+++ This bug was initially created as a clone of Bug #1417466 +++ Description of problem: There is a chance for the source brick to go down just after the new entry is created and before source brick is marked with necessary pending markers. If after this any I/O happens then new entry will become source and reverse heal will happen. To prevent this mark the pending xattrs before creating the new entry. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: --- Additional comment from Worker Ant on 2017-01-29 11:25:49 EST --- REVIEW: https://review.gluster.org/16474 (cluster/afr: Perform new entry mark before creating new entry) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu) --- Additional comment from Worker Ant on 2017-02-14 12:19:07 EST --- REVIEW: https://review.gluster.org/16474 (cluster/afr: Perform new entry mark before creating new entry) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) --- Additional comment from Worker Ant on 2017-02-16 10:24:34 EST --- COMMIT: https://review.gluster.org/16474 committed in master by Pranith Kumar Karampuri (pkarampu) ------ commit 6588204568ab73bf8456ca3b2eccf2ae1182fb95 Author: Pranith Kumar K <pkarampu> Date: Mon Jan 23 14:58:45 2017 +0530 cluster/afr: Perform new entry mark before creating new entry There is a chance for the source brick to go down just after the new entry is created and before source brick is marked with necessary pending markers. If after this any I/O happens then new entry will become source and reverse heal will happen. To prevent this mark the pending xattrs before creating the new entry. BUG: 1417466 Change-Id: I233b87e694d32e5d734df5a83b4d2ca711c17503 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: https://review.gluster.org/16474 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Ravishankar N <ravishankar> Reviewed-by: Krutika Dhananjay <kdhananj>
REVIEW: https://review.gluster.org/16646 (cluster/afr: Perform new entry mark before creating new entry) posted (#1) for review on release-3.10 by Pranith Kumar Karampuri (pkarampu)
COMMIT: https://review.gluster.org/16646 committed in release-3.10 by Shyamsundar Ranganathan (srangana) ------ commit e89f575ccdb7efebe34248af6982ebf4579cbab3 Author: Pranith Kumar K <pkarampu> Date: Mon Jan 23 14:58:45 2017 +0530 cluster/afr: Perform new entry mark before creating new entry There is a chance for the source brick to go down just after the new entry is created and before source brick is marked with necessary pending markers. If after this any I/O happens then new entry will become source and reverse heal will happen. To prevent this mark the pending xattrs before creating the new entry. >BUG: 1417466 >Change-Id: I233b87e694d32e5d734df5a83b4d2ca711c17503 >Signed-off-by: Pranith Kumar K <pkarampu> >Reviewed-on: https://review.gluster.org/16474 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >CentOS-regression: Gluster Build System <jenkins.org> >Reviewed-by: Ravishankar N <ravishankar> >Reviewed-by: Krutika Dhananjay <kdhananj> BUG: 1422942 Change-Id: I460caaa2c6571c4256e50421e48857e3c2769b4d Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: https://review.gluster.org/16646 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Shyamsundar Ranganathan <srangana>
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-3.10.0, please open a new bug report. glusterfs-3.10.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/gluster-users/2017-February/030119.html [2] https://www.gluster.org/pipermail/gluster-users/