Bug 763665 (GLUSTER-1933)
Summary: | Segfault while expansion of volume from distributed mirror | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Harshavardhana <fharshav> |
Component: | core | Assignee: | Amar Tumballi <amarts> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | urgent | ||
Version: | 3.1.0 | CC: | anush, cww, gluster-bugs, jacob, lakshmipathi, rabhat, vijay, vraman |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Harshavardhana
2010-10-12 19:14:37 UTC
This happened in 'cleanup_and_exit()' path, ie, a SIGTERM was issued to the process from glusterd anyways. Hence its not considered a blocker at the moment. There are many 'cleanup_and_exit()' path crashes which are known.. we are taking it as part of 3.1.1 release. No need to panic. (In reply to comment #1) > This happened in 'cleanup_and_exit()' path, ie, a SIGTERM was issued to the > process from glusterd anyways. Hence its not considered a blocker at the > moment. There are many 'cleanup_and_exit()' path crashes which are known.. we > are taking it as part of 3.1.1 release. No need to panic. Is that a rare case? in this scenario when we encountered Platform node was completely hosed resulting in access to mount point hung from nfs client. *** Bug 1908 has been marked as a duplicate of this bug. *** *** Bug 1892 has been marked as a duplicate of this bug. *** PATCH: http://patches.gluster.com/patch/5501 in master (io-stats: handle the case of 'cleanup_and_exit()' properly) verified with 3.1.1qa9 |