Bug 1393526
Summary: | [Ganesha] : Ganesha crashes intermittently during nfs-ganesha restarts. | |||
---|---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Ambarish <asoman> | |
Component: | io-threads | Assignee: | Pranith Kumar K <pkarampu> | |
Status: | CLOSED ERRATA | QA Contact: | Ambarish <asoman> | |
Severity: | high | Docs Contact: | ||
Priority: | medium | |||
Version: | rhgs-3.2 | CC: | amukherj, asoman, bturner, jthottan, ndevos, pkarampu, rgowdapp, rhinduja, rhs-bugs, skoduri, storage-qa-internal | |
Target Milestone: | --- | |||
Target Release: | RHGS 3.2.0 | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8.4-6 | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1396793 (view as bug list) | Environment: | ||
Last Closed: | 2017-03-23 06:17:50 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: | 1396793 | |||
Bug Blocks: | 1351528 |
Description
Ambarish
2016-11-09 18:24:51 UTC
Ambarish, If you happen to reproduce the issue, please take the core (using gdb) before running service stop/restart so as to compare the threads before and after the crash. Thanks! I tried it twice,but I could not reproduce the issue post setting client-io-threads to "off". The issue is a bit intermittent,so it's hard to say that with certainty ,though. (if that is or is not the culprit). Soumya, I tried the steps after keeping my volume in "Started" state,before setting up the Ganesha cluster and exporting the volume,twice on fresh setups,and I could not reproduce the crash on multiple tries of system service restarts. Thanks Amabrish. That almost confirms the theory that this crash is hit only if a volume is being exported via nfs-ganesha before it is even started. Since this is not a recommended configuration, lowering the priority of the bug for now. I suspect that probably when the volume is not started, the flow shall be glfs_init() -> xlator_init() of all the child subvols -> and then rpc_connection to brick which shall fail. Post which "glfs_fini" shall be called. May be since glfs_init() itself failed, graph would have not been setup and PARENT_DOWN may not have been sent to io-threads xlator, resulting in the dangling thread. This is just the theory I have on top of my mind. Will look through the code a bit. CCin Pranith too. I could not reproduce this crash on multiple tries gluster : glusterfs-3.8.4-10 ganesha : 2.4.1-3 Verified. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2017-0486.html |