Bug 203829
| Summary: | node fenced after einval messages | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Cluster Suite | Reporter: | Lenny Maiorani <lenny> |
| Component: | magma | Assignee: | Lon Hohberger <lhh> |
| Status: | CLOSED DUPLICATE | QA Contact: | Cluster QE <mspqa-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4 | CC: | cluster-maint, teigland |
| 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-10-05 20:05:25 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
Lenny Maiorani
2006-08-23 21:41:52 UTC
The DLM is producing those messages about the Magma lockspace. I'm not sure off the top of my head what they mean. The messages are warnings that usually indicate two (or more) nodes are repeatedly and quickly locking/unlocking the same lock. The dlm can generally deal with this, but it's something that we want to avoid when possible. (Some recent rgmanager changes were made to avoid situations like this by using lock conversions.) There's no direct link betweeen these messages and the node failing. What did cman report on the other nodes as the reason for this node being removed from the cluster and fenced? Correct, in the U4 magma plugin(s) + magma + rgmanager, we take a NL lock and attempt to promote it to EX in a loop (rather than the old behavior, which was to take a noqueue+EX in a loop until we got the lock). |