Red Hat GFS 5.2.1 -, Руководство администратора

Страница: 161 / 192

Appendix B. Basic GFS Examples 147
B.3.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.3.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.
B.3.3. Setup Process
The setup process for this example consists of the following steps:
1. Create pool configurations for the two file systems.
Create pool configuration files for each file system’s pool:
pool_gfs01
for the first file system,
and
pool_gfs02
for the second file system. The two files should look like the following:
poolname pool_gfs01
subpools 1