Installation guide

# For now, you need to set this up yourself first (e.g., with

'dmsetup')

# For example, you could make it return I/O errors using the 'error'

# target or make it return zeros.

missing_stripe_filler = "/dev/ioerror"

# How much stack (in KB) to reserve for use while devices suspended

reserved_stack = 256

# How much memory (in KB) to reserve for use while devices suspended

reserved_memory = 8192

# Nice value used while devices suspended

process_priority = -18

# If volume_list is defined, each LV is only activated if there is a

# match against the list.

# "vgname" and "vgname/lvname" are matched exactly.

# "@tag" matches any tag set in the LV or VG.

# "@*" matches if any tag defined on the host is also set in the LV

or VG

# volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]

# Size (in KB) of each copy operation when mirroring

mirror_region_size = 512

# 'mirror_image_fault_policy' and 'mirror_log_fault_policy' define

# how a device failure affecting a mirror is handled.

# A mirror is composed of mirror images (copies) and a log.

# A disk log ensures that a mirror does not need to be re-synced

# (all copies made the same) every time a machine reboots or crashes.

# In the event of a failure, the specified policy will be used to

# determine what happens:

# "remove" - Simply remove the faulty device and run without it. If

# the log device fails, the mirror would convert to using

# an in-memory log. This means the mirror will not

# remember its sync status across crashes/reboots and

# the entire mirror will be re-synced. If a

# mirror image fails, the mirror will convert to a

# non-mirrored device if there is only one remaining good

# copy.

# "allocate" - Remove the faulty device and try to allocate space on

# 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.

68 | www.redhat.com