Red Hat ENTERPRISE LINUX 5.1 - LVM ADMINISTRATION Manual page 94

Appendix B. The LVM Configuration Files
# determine what happens:
#
# "remove" - Simply remove the faulty device and run without it.
#
#
#
#
#
#
#
#
# "allocate" - Remove the faulty device and try to allocate space on
#
#
#
#
#
#
#
#
#
#
#
# "allocate_anywhere" - Operates like "allocate", but it does not
#
#
#
#
#
#
#
#
#
#
mirror_log_fault_policy = "allocate"
mirror_device_fault_policy = "remove"
}
####################
# Advanced section #
####################
# Metadata settings
#
# metadata {
# Default number of copies of metadata to hold on each PV.
2.
# You might want to override it from the command line with 0
82
the log device fails, the mirror would convert to using
an in-memory log.
remember its sync status across crashes/reboots and
the entire mirror will be re-synced.
mirror image fails, the mirror will convert to a
non-mirrored device if there is only one remaining good
copy.
a new device to be a replacement for the failed device.
Using this policy for the log is fast and maintains the
ability to remember sync state through crashes/reboots.
Using this policy for a mirror device is slow, as it
requires the mirror to resynchronize the devices, but it
will preserve the mirror characteristic of the device.
This policy acts like "remove" if no suitable device and
space can be allocated for the replacement.
Currently this is not implemented properly and behaves
similarly to:
require that the new space being allocated be on a
device is not part of the mirror.
failure, this could mean that the log is allocated on
the same device as a mirror device.
device, this could mean that the mirror device is
allocated on the same device as another mirror device.
This policy would not be wise for mirror devices
because it would break the redundant nature of the
mirror. This policy acts like "remove" if no suitable
device and space can be allocated for the replacement.
This means the mirror will not
For a log device
If
If a
For a mirror
0, 1 or