Bug 147682
Summary: | Filesystem hung while running moderate IO load | ||
---|---|---|---|
Product: | [Retired] Red Hat Cluster Suite | Reporter: | Dean Jansa <djansa> |
Component: | dlm | Assignee: | David Teigland <teigland> |
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4 | CC: | cluster-maint |
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: | 2006-02-02 14:52:18 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
Dean Jansa
2005-02-10 15:50:07 UTC
Dave, if this looks more like a GFS issue, please reassign. I had to pick one, so I'm picking on you. :) Versions of the modules: DLM 2.6.9-18.0 (built Feb 9 2005 14:56:57) Lock_DLM (built Feb 9 2005 15:07:12) GFS 2.6.9-18.3 (built Feb 9 2005 15:07:30) CMAN 2.6.9-17.2 (built Feb 9 2005 14:52:26) Lock_Harness 2.6.9-18.3 (built Feb 9 2005 15:07:09) I'm guessing this is a plock/flock problem. A dump of the dlm locks would help here: echo "name of lockspace" >> /proc/cluster/dlm_locks cat /proc/cluster/dlm_locks > locks.txt Is there a "quick" way for me to run this load on my machines? Hmm, all of the /proc/cluster/dlm_locks are empty.... As for the quick was to run the load.... You have the sistina-test tree correct? (You run revolver if I recall) You can run sistina-test/vedder/bin/vedder -R <your cluster resource file> -l <path to sistina-test root> -S QUICK For example I ran: vedder -R ../../var/share/resource_files/morph-cluster.xml -l ~/src/sistina-test -S QUICK Having said that... Not sure if you will hit it, I have not tried to reproduce it yet. Oops, the dlm_locks are not empty. Have to paste the correct lockspace name... I'm gathering. Dave, you can find the dlm_lock output from each node at: /home/msp/djansa/pub/bugs/147682/morph*.dlm_locks The lock dump shows one problem that I've just checked in a fix for. It was related to the quota lock. I don't know if it explains the hang, though; would probably need a kdb trace to know for sure. Neither Dean nor I have been able to reproduce this since the fix mentioned above. That could indicate that the problem is solved, the problem is difficult to reproduce or both. |