Red Hat GFS 6.0 Administrator's Manual page 172

158
Note
If your cluster is running Red Hat GFS 6.0 for Red Hat Enterprise Linux 3 Update 5
and later, you can use the optional
rather than relying on an IP address from
optional
Example 6-26. Refer to Table 6-3 for syntax description of the
d. Create the
method(s) used by the GFS cluster. The file should look like the following:
fence_devices {
apc {
agent = "fence_apc"
ipaddr = "10.0.1.10"
login = "apc"
passwd = "apc"
}
}
6. Create the CCS Archive on the CCA Device.
Note
This step only needs to be done once and from a single node. It should not be performed every
time the cluster is restarted.
Use the
ccs_tool
n01# ccs_tool create /root/alpha /dev/pool/alpha_cca
Initializing device for first time use... done.
7. Start the CCS daemon (
Note
This step must be performed each time the cluster is rebooted.
The CCA device must be specified when starting
n01# ccsd -d /dev/pool/alpha_cca
n02# ccsd -d /dev/pool/alpha_cca
n03# ccsd -d /dev/pool/alpha_cca
lcksrv# ccsd -d /dev/pool/alpha_cca
8. At each node, start the LOCK_GULM server. For example:
n01# lock_gulmd
lcksrv# lock_gulmd
9. Create the GFS file systems.
Create the first file system on
two file systems are
parameter, refer to the file format in Figure 6-23 and the example in
usedev
file. This file contains information required for the fencing
fence.ccs
command to create the archive from the CCS configuration files:
) on all the nodes.
ccsd
pool_gfs01
and
gfs01 gfs02
Appendix C. Basic GFS Examples
parameter to explicitly specify an IP address
usedev
libresolv
.
ccsd
and the second on
, respectively, as shown in the example:
. For more information about the
parameter.
usedev
. The names of the
pool_gfs02