Bug 1243187
Summary: | Disperse volume : client glusterfs crashed while running IO | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Pranith Kumar K <pkarampu> | |
Component: | disperse | Assignee: | Pranith Kumar K <pkarampu> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | mainline | CC: | annair, asrivast, bugs, byarlaga, gluster-bugs, jahernan, nsathyan, pkarampu, rhs-bugs | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1242423 | |||
: | 1246121 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 13:24:08 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: | 1242423 | |||
Bug Blocks: | 1223636, 1246121 |
Comment 1
Pranith Kumar K
2015-07-15 00:58:34 UTC
REVIEW: http://review.gluster.org/6459 (timer: fix race between gf_timer_call_cancel() and gf_timer_proc()) posted (#2) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/11670 (cluster/ec: Handle race between unlock-timer, new lock) posted (#1) for review on master by Pranith Kumar Karampuri (pkarampu) REVIEW: http://review.gluster.org/6459 (timer: fix race between gf_timer_call_cancel() and gf_timer_proc()) posted (#4) for review on master by Pranith Kumar Karampuri (pkarampu) COMMIT: http://review.gluster.org/11670 committed in master by Xavier Hernandez (xhernandez) ------ commit 332cb6a6901c68f0c79070d7103cc7a728ea6d26 Author: Pranith Kumar K <pkarampu> Date: Wed Jul 15 06:16:54 2015 +0530 cluster/ec: Handle race between unlock-timer, new lock Problem: New lock could come at the time timer is on the way to unlock. This was leading to crash in timer thread because thread executing new lock can free up the timer_link->fop and then timer thread will try to access structures already freed. Fix: If the timer event is fired, set lock->release to true and wait for unlock to complete. Thanks to Xavi and Bhaskar for helping in confirming that this race is the RC. Thanks to Kritika for pointing out and explaining how Avati's patch can be used to fix this bug. Change-Id: I45fa5470bbc1f03b5f3d133e26d1e0ab24303378 BUG: 1243187 Signed-off-by: Pranith Kumar K <pkarampu> Reviewed-on: http://review.gluster.org/11670 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Xavier Hernandez <xhernandez> Tested-by: NetBSD Build System <jenkins.org> Fix for this BZ is already present in a GlusterFS release. You can find clone of this BZ, fixed in a GlusterFS release and closed. Hence closing this mainline BZ as well. 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 |