Red Hat GFS 6.0 -, Administrator'S Manual

Page: 172 / 192

158 Appendix C. Basic GFS Examples
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
usedev
parameter to explicitly specify an IP address
rather than relying on an IP address from
libresolv
. For more information about the
optional
usedev
parameter, refer to the file format in Figure 6-23 and the example in
Example 6-26. Refer to Table 6-3 for syntax description of the
usedev
parameter.
d. Create the
fence.ccs
file. This file contains information required for the fencing
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
command to create the archive from the CCS configuration files:
n01#
ccs_tool create /root/alpha /dev/pool/alpha_cca
Initializing device for first time use... done.
7. Start the CCS daemon (
ccsd
) on all the nodes.
Note
This step must be performed each time the cluster is rebooted.
The CCA device must be specified when starting
ccsd
.
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
pool_gfs01
and the second on
pool_gfs02
. The names of the
two file systems are
gfs01
and
gfs02
, respectively, as shown in the example: