+++ This bug was initially created as a clone of Bug #1455104 +++ Description of problem: With new synchronization behaviour where read inodelk and RW entrylk is taken on hashed subvol, self heal directory would fail sometimes when hashed subvol is not populated. Version-Release number of selected component (if applicable): mainline How reproducible: Sometimes Steps to Reproduce: 1. Create distribute volume 2. Mount and initiate I/O and lookup in parallel Actual results: Self heal fails sometimes Expected results: Self heal should not fail. Additional info: --- Additional comment from Worker Ant on 2017-05-24 05:45:29 EDT --- REVIEW: https://review.gluster.org/17381 (features/dht: Initialize local hashed_subvol) posted (#1) for review on master by Kotresh HR (khiremat) --- Additional comment from Worker Ant on 2017-05-25 00:21:16 EDT --- COMMIT: https://review.gluster.org/17381 committed in master by Raghavendra G (rgowdapp) ------ commit 90df37558d488f9a794f62ed74ec6d72879ed895 Author: Kotresh HR <khiremat> Date: Wed May 24 03:17:33 2017 -0400 features/dht: Initialize local hashed_subvol Self heal directory code path doesn't always have local->hashed_subvol populated. Populating the same which otherwise would fail the self heal. Change-Id: I03b64709fd7a68e28f9e7438243e817c53c6ef5d BUG: 1455104 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: https://review.gluster.org/17381 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Amar Tumballi <amarts> Reviewed-by: N Balachandran <nbalacha> Reviewed-by: Raghavendra G <rgowdapp>
Patch: https://review.gluster.org/#/c/17388/
COMMIT: https://review.gluster.org/17388 committed in release-3.11 by Shyamsundar Ranganathan (srangana) ------ commit bf335dd1fbb67e852bf974fc42a270d772fb6bb9 Author: Kotresh HR <khiremat> Date: Wed May 24 03:17:33 2017 -0400 features/dht: Initialize local hashed_subvol Self heal directory code path doesn't always have local->hashed_subvol populated. Populating the same which otherwise would fail the self heal. > Change-Id: I03b64709fd7a68e28f9e7438243e817c53c6ef5d > BUG: 1455104 > Signed-off-by: Kotresh HR <khiremat> > Reviewed-on: https://review.gluster.org/17381 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Amar Tumballi <amarts> > Reviewed-by: N Balachandran <nbalacha> > Reviewed-by: Raghavendra G <rgowdapp> (cherry picked from commit 90df37558d488f9a794f62ed74ec6d72879ed895) Change-Id: I03b64709fd7a68e28f9e7438243e817c53c6ef5d BUG: 1455423 Signed-off-by: Kotresh HR <khiremat> Reviewed-on: https://review.gluster.org/17388 Smoke: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.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-3.11.0, please open a new bug report. glusterfs-3.11.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/2017-May/000073.html [2] https://www.gluster.org/pipermail/gluster-users/