Red Hat CLUSTER SUITE 4.7 - CLUSTER LVM ADMINISTRATORS, Manual

Page: 92 / 108

Appendix B. The LVM Configuration Files
80
# If we can't communicate with device-mapper, should we try running
# the LVM1 tools?
# This option only applies to 2.4 kernels and is provided to help you
# switch between device-mapper kernels and LVM1 kernels.
# The LVM1 tools need to be installed with .lvm1 suffices
# e.g. vgscan.lvm1 and they will stop working after you start using
# the new lvm2 on-disk metadata format.
# The default value is set when the tools are built.
# fallback_to_lvm1 = 0
# The default metadata format that commands should use - "lvm1" or
"lvm2".
# The command line override is -M1 or -M2.
# Defaults to "lvm1" if compiled in, else "lvm2".
# format = "lvm1"
# Location of proc filesystem
proc = "/proc"
# Type of locking to use. Defaults to local file-based locking (1).
# Turn locking off by setting to 0 (dangerous: risks metadata
corruption
# if LVM2 commands get run concurrently).
# Type 2 uses the external shared library locking_library.
# Type 3 uses built-in clustered locking.
locking_type = 1
# If using external locking (type 2) and initialisation fails,
# with this set to 1 an attempt will be made to use the built-in
# clustered locking.
# If you are using a customised locking_library you should set this
to 0.
fallback_to_clustered_locking = 1
# If an attempt to initialise type 2 or type 3 locking failed,
perhaps
# because cluster components such as clvmd are not running, with this
set
# to 1 an attempt will be made to use local file-based locking (type
1).
# If this succeeds, only commands against local volume groups will
proceed.
# Volume Groups marked as clustered will be ignored.
fallback_to_local_locking = 1
# Local non-LV directory that holds file-based locks while commands
are
# in progress. A directory like /tmp that may get wiped on reboot is
OK.
locking_dir = "/var/lock/lvm"