Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 453594 - wrong start order: clvmd starts after qdiskd
Summary: wrong start order: clvmd starts after qdiskd
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: lvm2-cluster
Version: 5.2
Hardware: All
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: LVM and device-mapper development team
QA Contact: Cluster QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-01 14:25 UTC by Herbert L. Plankl
Modified: 2010-07-23 14:36 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-07-23 14:35:58 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Herbert L. Plankl 2008-07-01 14:25:03 UTC
Description of problem:
I'm using a RHEL5.2 Cluster with lvm2, gfs2 and qdiskd (cluster designed for 2
datacentres).
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
works fine.

Here are my changes:

qdiskd:
from: "# chkconfig: - 22 78" to: "# chkconfig: - 24 76"

clvmd:
from "# chkconfig: - 24 76" to: "# chkconfig: - 22 78"


Version-Release number of selected component (if applicable):
RHEL5.2

Comment 3 Lon Hohberger 2010-07-23 14:35:58 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.


Note You need to log in before you can comment on or make changes to this bug.