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

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

Chapter 3. Installing System Software 17
Note
The GFS kernel modules need to be loaded every time a GFS node is started. It is recommended
that you use a startup script to automate loading the GFS kernel modules.
Note
The procedures in this section are for a GFS configuration that uses LOCK_GULM. If you are using
LOCK_NOLOCK, refer to Appendix B Basic GFS Examples for information about which GFS kernel
modules you should load.
Note
When loading the GFS kernel modules you may see warning messages indicating missing or non-
GPL licenses. The messages are not related to the GFS license and can be ignored.
To load the GFS kernel modules, follow the steps in Table 3-3. The steps in Table 3-3 use
modprobe
commands to load the GFS kernel modules; all dependent modules will be loaded automatically.
Alternatively, you can load the GFS kernel modules by following the steps in Table 3-4 . The steps in
Table 3-4 use
insmod
commands to load the GFS kernel modules.
Step Command Description
1.
depmod -a
Run this only once after RPMs are installed.
2.
modprobe pool
Loads
pool.o
and dependent files.
3.
modprobe lock_gulm
Loads
lock_gulm.o
and dependent files.
4.
modprobe gfs
Loads
gfs.o
and dependent files.
5.
lsmod
Verifies that all GFS kernel modules are loaded. This
shows a listing of currently loaded modules. It
should display all the modules loaded in the previous
steps and other system kernel modules.
Table 3-3. Loading GFS Kernel Modules
Step Command Description
1.
insmod ccs
Loads the
ccs.o
module.
2.
insmod pool
Loads the
pool.o
module.
3. insmod lock_harness Loads the
lock_harness.o
module.