Comparing Ccs Configuration Files To A Ccs Archive; Changing Ccs Configuration Files - Red Hat GFS 5.2.1 Administrator's Manual

74
7.3.2.2. Example
This example causes the CCS files contained on the CCA device,
listed.
ccs_tool list /dev/pool/alpha_cca
7.3.3. Comparing CCS Configuration Files to a CCS Archive
The
ccs_tool diff
the configuration files in a CCS archive. The output from the
for each corresponding file in the specified directory and the CCS archive.
7.3.3.1. Usage
ccs_tool diff CCADevice [Directory]
CCADevice
Specifies the name of the CCA device.
Directory
The relative path to the directory containing the CCS files for the cluster.
7.3.3.2. Example
In this example, the CCS configuration files in directory
figuration files in CCA device
ccs_tool diff /dev/pool/alpha_cca /root/alpha/
7.4. Changing CCS Configuration Files
Based on the LOCK_GULM locking protocol, the following list defines what can or cannot be
changed in a CCS archive while a cluster is running. There are no restrictions to making changes
to configuration files when the cluster is offline.
New nodes can be defined in the
•
Unused node definitions can be removed from the
•
New fencing devices can be defined in the
•
The locking servers array (
•
changed.
The fencing parameters for an existing node definition in
•
The IP address of an existing node definition in the
•
node does not have any GFS file systems mounted and is not running a LOCK_GULM server.
command can be used to compare a directory of CCS configuration files with
/dev/pool/alpha_cca
nodes.ccs
servers =
Chapter 7. Using the Cluster Configuration System
ccs_tool diff
/root/alpha/
.
file.
nodes.ccs
file.
fence.ccs
) in
cluster.ccs:cluster/lock_gulm
nodes.ccs
nodes.ccs
/dev/pool/alpha_cca
command is displayed
are compared with the con-
file.
can be changed.
file can only be changed if the
, to be
cannot be