Red Hat GFS 6.0 -, Administrator'S Manual

Page: 139 / 192

Chapter 11. Using GNBD 125
Node Deployment CCS File Location
GFS dedicated GNBD, local, or FC-attached storage
GFS with lock server Local or FC-attached storage only
GNBD server dedicated Local or FC-attached storage only
GNBD server with lock server Local or FC-attached storage only
Lock server dedicated Local or FC-attached storage only
Table 11-1. CCS File Location for GNBD Multipath Cluster
Before a GNBD client node can activate (using the
pool_assemble
command) a GNBD-multipath
pool, it must activate the GNBD-exported CCS pool and start
ccsd
and
lock_gulmd
. The following
example shows activating an GNBD-exported CCS pool labeled as
CCS
:
#
pool_assemble CCS
11.2.4. Fencing GNBD Server Nodes
GNBD server nodes must be fenced using a fencing method that physically removes the nodes from
the network. To physically remove a GNBD server node, you can use any of the following fencing
devices: APC MasterSwitch (
fence_apc
fence agent), WTI NPS (
fence_wti
fence agent),
Brocade FC switch (
fence_brocade
fence agent), McData FC switch (
fence_mcdata
fence
agent), Vixel FC switch (
fence_vixel
fence agent), HP RILOE (
fence_rib
fence agent), or
xCAT (
fence_xcat
fence agent). You cannot use the GNBD fencing device (
fence_gnbd
fence
agent) to fence a GNBD server node. For information about configuring fencing for GNBD server
nodes, refer to Chapter 6 Creating the Cluster Configuration System Files .
11.3. Running GFS on a GNBD Server Node
You can run GFS on a GNBD server node, with some restrictions. In addition, running GFS on a
GNBD server node reduces performance. The following restrictions apply when running GFS on a
GNBD server node.
Important
When running GFS on a GNBD server node you must follow the restrictions listed; otherwise, the
GNBD server node will fail.
Note
You may need to increase the timeout period on the exported GNBDs to accommodate reduced
performance. The need to increase the timeout period depends on the quality of the hardware.