Red Hat GFS 5.2.1 -, Administrator'S Manual

Page: 88 / 192

74 Chapter 7. Using the Cluster Configuration System
7.3.2.2. Example
This example causes the CCS files contained on the CCA device,
/dev/pool/alpha_cca
, to be
listed.
ccs_tool list /dev/pool/alpha_cca
7.3.3. Comparing CCS Configuration Files to a CCS Archive
The
ccs_tool diff
command can be used to compare a directory of CCS configuration files with
the configuration files in a CCS archive. The output from the
ccs_tool diff
command is displayed
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
/root/alpha/
are compared with the con-
figuration files in CCA device
/dev/pool/alpha_cca
.
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
nodes.ccs
file.
•
Unused node definitions can be removed from the
nodes.ccs
file.
•
New fencing devices can be defined in the
fence.ccs
file.
•
The locking servers array (
servers =
) in
cluster.ccs:cluster/lock_gulm
cannot be
changed.
•
The fencing parameters for an existing node definition in
nodes.ccs
can be changed.
•
The IP address of an existing node definition in the
nodes.ccs
file can only be changed if the
node does not have any GFS file systems mounted and is not running a LOCK_GULM server.