Bug 480013
Summary: | GFS: httpd processes get hanged in D state | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Balázs Miklós <mbalazs> |
Component: | GFS-kernel | Assignee: | Robert Peterson <rpeterso> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Cluster QE <mspqa-list> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4 | CC: | edamato, mbalazs, szivan |
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: | 2009-07-15 18:47:01 UTC | 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
Balázs Miklós
2009-01-14 15:50:58 UTC
In order to analyze the hang, I need to get the following information: 1. A dump of all GFS "glocks" from all nodes in the cluster. Please see: http://sources.redhat.com/cluster/wiki/FAQ/LockManager#lock_dump_gfs 2. A dump of all dlm locks from all nodes in the cluster. Please see: http://sources.redhat.com/cluster/wiki/FAQ/LockManager#lock_dump_dlm 3. Process call trace output from all nodes in the cluster from sysrq-t output. The easiest way to collect that is to do this command: echo "t" > /proc/sysrq-trigger and capture/save the console output. Please be aware that triggering the sysrq-t output can cause the system to hang and be unresponsive. Therefore, other nodes may think the system is dead and try to fence it. So you may have to temporarily disable fencing in order to collect the complete output. In NEEDINFO for six months; closing INSUFFICIENT_DATA. |