Red Hat Bugzilla – Bug 453594
wrong start order: clvmd starts after qdiskd
Last modified: 2010-07-23 10:36:36 EDT
Description of problem:
I'm using a RHEL5.2 Cluster with lvm2, gfs2 and qdiskd (cluster designed for 2
To be able to use a (c)mirrored-qdisk I'm using a clustered volume-group for a
lv which is used by qdiskd. I don't know why, but per default qdiskd starts
before clvmd and so qdiskd cannot be started. I changed the order and everything
Here are my changes:
from: "# chkconfig: - 22 78" to: "# chkconfig: - 24 76"
from "# chkconfig: - 24 76" to: "# chkconfig: - 22 78"
Version-Release number of selected component (if applicable):
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.