Appendix B. Basic GFS Examples
153
B.4.2.1. Kernel Installed
An appropriate kernel must be installed and running on each node. Refer to Section 3.2.1
Installing a
Linux Kernel
for more information about installing a Linux kernel.
B.4.2.2. GFS RPM Installed
The GFS RPMs must be installed, and all GFS commands, daemons and fencing agents must be
accessible via root’s search path.
B.4.2.3. Kernel Modules Loaded
Each node must have the following kernel modules loaded:
•
ccs.o
•
gfs.o
•
lock_harness.o
•
lock_gulm.o
•
pool.o
Note
The GFS kernel modules must be loaded every time a node is rebooted. If they are not loaded, GFS
will not function.
You can confirm that the modules have been loaded by running the
lsmod
command. If you need to
load the kernel modules, it is recommended that you use the
modprobe
command, using the following
syntax:
modprobe
ModuleName
The following example shows the
modprobe
command being used for loading the
ccs.o
module:
#
modprobe ccs
Note
When using
modprobe
, do not specify the
.o
suffix as part of the module name. If the response to
the
modprobe
command displays a message about being unable to find a module, run the
depmod
-a
command and try loading the module again.
Summary of Contents for GFS 5.2.1 -
Page 1: ...Red Hat GFS 5 2 1 Administrator s Guide...
Page 8: ......
Page 14: ...vi Introduction...
Page 24: ...10 Chapter 1 GFS Overview...
Page 36: ...22 Chapter 4 Initial Configuration...
Page 84: ...70 Chapter 6 Creating the Cluster Configuration System Files...
Page 96: ...82 Chapter 8 Using Clustering and Locking Systems...
Page 126: ...112 Chapter 10 Using the Fencing System...
Page 132: ...118 Chapter 11 Using GNBD...
Page 144: ...130 Appendix A Upgrading GFS...
Page 184: ...170 Appendix B Basic GFS Examples...
Page 190: ......
Page 192: ...178...