Bug 1232693
Summary: | glusterd crashed when testing heal full on replaced disks | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Anand Nekkunti <anekkunt> |
Component: | glusterd | Assignee: | Satish Mohan <smohan> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | mainline | CC: | amukherj, atalur, bugs, nlevinki, sankarshan, sasundar, smohan, spandura, vbellur |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | GlusterD | ||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 1231635 | Environment: | |
Last Closed: | 2016-06-16 13:13:39 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1231635, 1233041 | ||
Bug Blocks: |
Comment 1
Anand Avati
2015-06-17 12:39:25 UTC
REVIEW: http://review.gluster.org/11306 (glusterd: Removing sync lock and unlock inside rcu read critical section) posted (#1) for review on release-3.7 by Anand Nekkunti (anekkunt) COMMIT: http://review.gluster.org/11276 committed in master by Atin Mukherjee (amukherj) ------ commit 8ddf7f2669779cee460f1e008cdb62671cf15a40 Author: anand <anekkunt> Date: Wed Jun 17 16:11:48 2015 +0530 glusterd: Removing sync lock and unlock inside rcu read critical section Issue : Glsuterd was crashing during peer probe. RCA : In glusterd, we are using big lock which is implemented based on sync task frame work for thread synchronization, sync task frame work swap the threads if there is no worker pool threads available. Due to this rcu lock and rcu unlock was happening in different threads (urcu-bp will not allow this), resulting into glusterd crash. fix : Removing sync lock and unlock inside rcu read critical section, which was left out by http://review.gluster.org/#/c/10285/ patch. Change-Id: Id358dfcc797335bcd3b491c3129017b2caa826eb BUG: 1232693 Signed-off-by: anand <anekkunt> Reviewed-on: http://review.gluster.org/11276 Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Krishnan Parthasarathi <kparthas> Tested-by: NetBSD 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.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |