Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 243475 - Clarify when to start and stop clvmd (RHEL 5)
Clarify when to start and stop clvmd (RHEL 5)
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: Documentation-cluster (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Paul Kennedy
Cluster QE
: Documentation
Depends On:
  Show dependency treegraph
Reported: 2007-06-08 17:44 EDT by Paul Kennedy
Modified: 2015-04-19 20:47 EDT (History)
3 users (show)

See Also:
Fixed In Version: RHEL 5.1, RHEL 5.0
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-01-16 11:07:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Paul Kennedy 2007-06-08 17:44:39 EDT
+++ This bug was initially created as a clone of Bug #243474 +++

Same bug as in cluster suite doc for RHEL 4.

Description of problem:
The Red Hat Cluster Suite cluster administration document should clarify when it
is necessary to start and stop clvmd when starting and stopping a cluster.

Starting and stopping clvmd is required only if CLVM is used as a volume manager.

For example:

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


Release number: rh-cs(EN)-5 (2007-01-23T09:05)

Additional info:
Several procedures in the book noted includes starting and stopping a cluster.
Make sure all instances have been corrected.
Comment 2 Paul Kennedy 2007-10-17 15:29:53 EDT
For each instance of "service clvmd start" and "service clvmd stop", appended
the following:
"if CLVM has been used to create clustered volumes"

Comment 3 Nate Straz 2007-12-13 12:45:38 EST
Moving all RHCS ver 5 bugs to RHEL 5 so we can remove RHCS v5 which never existed.
Comment 4 Paul Kennedy 2008-01-16 11:07:31 EST
Fixed in all RHEL 5 documentation. Posted here:

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