Bug 453594
Summary: | wrong start order: clvmd starts after qdiskd | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Herbert L. Plankl <h.plankl> |
Component: | lvm2-cluster | Assignee: | LVM and device-mapper development team <lvm-team> |
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | agk, ccaulfie, cluster-maint, dwysocha, heinzm, jbrassow, joe.thornber, mbroz, mhideo, prajnoha, prockai |
Target Milestone: | rc | Keywords: | Documentation |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-07-23 14:35:58 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
Herbert L. Plankl
2008-07-01 14:25:03 UTC
qdiskd is required for quorum and does not run on top of clvmd without being started manually; this is documented in section 1.4 under "Limitations" in the qdisk man page: * Currently, the quorum disk daemon is difficult to use with CLVM if the quorum disk resides on a CLVM logical volume. CLVM requires a quo- rate cluster to correctly operate, which introduces a chicken-and-egg problem for starting the cluster: CLVM needs quorum, but the quorum daemon needs CLVM (if and only if the quorum device lies on CLVM-managed storage). One way to work around this is to *not* set the cluster’s expected votes to include the quorum daemon’s votes. Bring all nodes online, and start the quorum daemon *after* the whole cluster is run- ning. This will allow the expected votes to increase naturally. |