|
- {%- from "linux/map.jinja" import storage with context %}
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- config {
-
-
-
-
-
-
-
-
- checks = 1
-
-
-
- abort_on_errors = 0
-
-
-
- profile_dir = "/etc/lvm/profile"
- }
-
-
-
- devices {
-
-
-
-
-
- dir = "/dev"
-
-
-
-
- scan = [ "/dev" ]
-
-
-
-
-
-
-
-
-
- obtain_device_list_from_udev = 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- external_device_info_source = "none"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- filter = [ {%- for vgname, vg in storage.lvm.items() %}{%- if vg.get('enabled', True) %}{%- for dev in vg.devices %}"a|{{ dev }}*|"{%- if not loop.last %},{%- endif %}{%- endfor %}{%- endif %}{%- endfor %}, "r|.*|" ]
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- cache_dir = "/run/lvm"
-
-
-
- cache_file_prefix = ""
-
-
-
- write_cache_state = 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- sysfs_scan = 1
-
-
-
- multipath_component_detection = 1
-
-
-
- md_component_detection = 1
-
-
-
-
-
- fw_raid_component_detection = 0
-
-
-
-
- md_chunk_alignment = 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- data_alignment_detection = 1
-
-
-
-
-
-
-
-
- data_alignment = 0
-
-
-
-
-
-
-
-
-
-
- data_alignment_offset_detection = 1
-
-
-
-
-
- ignore_suspended_devices = 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ignore_lvm_mirrors = 1
-
-
-
-
-
-
-
- disable_after_error_count = 0
-
-
-
- require_restorefile_with_uuid = 1
-
-
-
-
-
-
- pv_min_size = 2048
-
-
-
-
-
-
-
-
-
-
-
-
- issue_discards = 1
- }
-
-
-
- allocation {
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- maximise_cling = 1
-
-
-
-
-
-
-
-
-
- use_blkid_wiping = 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- wipe_signatures_when_zeroing_new_lvs = 1
-
-
-
-
- mirror_logs_require_separate_pvs = 0
-
-
-
- cache_pool_metadata_require_separate_pvs = 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- thin_pool_metadata_require_separate_pvs = 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- }
-
-
-
- log {
-
-
-
- verbose = 0
-
-
-
-
-
-
-
-
-
-
- silent = 0
-
-
-
- syslog = 1
-
-
-
-
-
-
-
- overwrite = 0
-
-
-
-
-
- level = 0
-
-
-
- indent = 1
-
-
-
- command_names = 0
-
-
-
-
-
-
-
- prefix = " "
-
-
-
-
- activation = 0
-
-
-
-
-
-
-
- debug_classes = [ "memory", "devices", "activation", "allocation", "lvmetad", "metadata", "cache", "locking", "lvmpolld" ]
- }
-
-
-
-
-
-
- backup {
-
-
-
-
- backup = 1
-
-
-
-
- backup_dir = "/etc/lvm/backup"
-
-
-
-
- archive = 1
-
-
-
-
- archive_dir = "/etc/lvm/archive"
-
-
-
- retain_min = 10
-
-
-
- retain_days = 30
- }
-
-
-
- shell {
-
-
-
- history_size = 100
- }
-
-
-
- global {
-
-
-
-
- umask = 077
-
-
-
-
- test = 0
-
-
-
- units = "h"
-
-
-
-
-
-
-
- si_unit_consistency = 1
-
-
-
-
-
- suffix = 1
-
-
-
-
-
-
-
- activation = 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- proc = "/proc"
-
- # Configuration option global/etc.
- # Location of /etc system configuration directory.
- etc = "/etc"
-
- # Configuration option global/locking_type.
- # Type of locking to use.
- #
- # Accepted values:
- # 0
- # Turns off locking. Warning: this risks metadata corruption if
- # commands run concurrently.
- # 1
- # LVM uses local file-based locking, the standard mode.
- # 2
- # LVM uses the external shared library locking_library.
- # 3
- # LVM uses built-in clustered locking with clvmd.
- # This is incompatible with lvmetad. If use_lvmetad is enabled,
- # LVM prints a warning and disables lvmetad use.
- # 4
- # LVM uses read-only locking which forbids any operations that
- # might change metadata.
- # 5
- # Offers dummy locking for tools that do not need any locks.
- # You should not need to set this directly; the tools will select
- # when to use it instead of the configured locking_type.
- # Do not use lvmetad or the kernel device-mapper driver with this
- # locking type. It is used by the --readonly option that offers
- # read-only access to Volume Group metadata that cannot be locked
- # safely because it belongs to an inaccessible domain and might be
- # in use, for example a virtual machine image or a disk that is
- # shared by a clustered machine.
- #
- locking_type = 1
-
- # Configuration option global/wait_for_locks.
- # When disabled, fail if a lock request would block.
- wait_for_locks = 1
-
- # Configuration option global/fallback_to_clustered_locking.
- # Attempt to use built-in cluster locking if locking_type 2 fails.
- # If using external locking (type 2) and initialisation fails, with
- # this enabled, an attempt will be made to use the built-in clustered
- # locking. Disable this if using a customised locking_library.
- fallback_to_clustered_locking = 1
-
- # Configuration option global/fallback_to_local_locking.
- # Use locking_type 1 (local) if locking_type 2 or 3 fail.
- # If an attempt to initialise type 2 or type 3 locking failed, perhaps
- # because cluster components such as clvmd are not running, with this
- # enabled, an attempt will be made to use local file-based locking
- # (type 1). If this succeeds, only commands against local VGs will
- # proceed. VGs marked as clustered will be ignored.
- fallback_to_local_locking = 1
-
- # Configuration option global/locking_dir.
- # Directory to use for LVM command file locks.
- # 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 = "/run/lock/lvm"
-
- # Configuration option global/prioritise_write_locks.
- # Allow quicker VG write access during high volume read access.
- # When there are competing read-only and read-write access requests for
- # a volume group's metadata, instead of always granting the read-only
- # requests immediately, delay them to allow the read-write requests to
- # be serviced. Without this setting, write access may be stalled by a
- # high volume of read-only requests. This option only affects
- # locking_type 1 viz. local file-based locking.
- prioritise_write_locks = 1
-
- # Configuration option global/library_dir.
- # Search this directory first for shared libraries.
- # This configuration option does not have a default value defined.
-
- # Configuration option global/locking_library.
- # The external locking library to use for locking_type 2.
- # This configuration option has an automatic default value.
- # locking_library = "liblvm2clusterlock.so"
-
- # Configuration option global/abort_on_internal_errors.
- # Abort a command that encounters an internal error.
- # Treat any internal errors as fatal errors, aborting the process that
- # encountered the internal error. Please only enable for debugging.
- abort_on_internal_errors = 0
-
- # Configuration option global/detect_internal_vg_cache_corruption.
- # Internal verification of VG structures.
- # Check if CRC matches when a parsed VG is used multiple times. This
- # is useful to catch unexpected changes to cached VG structures.
- # Please only enable for debugging.
- detect_internal_vg_cache_corruption = 0
-
- # Configuration option global/metadata_read_only.
- # No operations that change on-disk metadata are permitted.
- # Additionally, read-only commands that encounter metadata in need of
- # repair will still be allowed to proceed exactly as if the repair had
- # been performed (except for the unchanged vg_seqno). Inappropriate
- # use could mess up your system, so seek advice first!
- metadata_read_only = 0
-
- # Configuration option global/mirror_segtype_default.
- # The segment type used by the short mirroring option -m.
- # The --type mirror|raid1 option overrides this setting.
- #
- # Accepted values:
- # mirror
- # The original RAID1 implementation from LVM/DM. It is
- # characterized by a flexible log solution (core, disk, mirrored),
- # and by the necessity to block I/O while handling a failure.
- # There is an inherent race in the dmeventd failure handling logic
- # with snapshots of devices using this type of RAID1 that in the
- # worst case could cause a deadlock. (Also see
- # devices/ignore_lvm_mirrors.)
- # raid1
- # This is a newer RAID1 implementation using the MD RAID1
- # personality through device-mapper. It is characterized by a
- # lack of log options. (A log is always allocated for every
- # device and they are placed on the same device as the image,
- # so no separate devices are required.) This mirror
- # implementation does not require I/O to be blocked while
- # handling a failure. This mirror implementation is not
- # cluster-aware and cannot be used in a shared (active/active)
- # fashion in a cluster.
- #
- mirror_segtype_default = "raid1"
-
- # Configuration option global/raid10_segtype_default.
- # The segment type used by the -i -m combination.
- # The --type raid10|mirror option overrides this setting.
- # The --stripes/-i and --mirrors/-m options can both be specified
- # during the creation of a logical volume to use both striping and
- # mirroring for the LV. There are two different implementations.
- #
- # Accepted values:
- # raid10
- # LVM uses MD's RAID10 personality through DM. This is the
- # preferred option.
- # mirror
- # LVM layers the 'mirror' and 'stripe' segment types. The layering
- # is done by creating a mirror LV on top of striped sub-LVs,
- # effectively creating a RAID 0+1 array. The layering is suboptimal
- # in terms of providing redundancy and performance.
- #
- raid10_segtype_default = "raid10"
-
- # Configuration option global/sparse_segtype_default.
- # The segment type used by the -V -L combination.
- # The --type snapshot|thin option overrides this setting.
- # The combination of -V and -L options creates a sparse LV. There are
- # two different implementations.
- #
- # Accepted values:
- # snapshot
- # The original snapshot implementation from LVM/DM. It uses an old
- # snapshot that mixes data and metadata within a single COW
- # storage volume and performs poorly when the size of stored data
- # passes hundreds of MB.
- # thin
- # A newer implementation that uses thin provisioning. It has a
- # bigger minimal chunk size (64KiB) and uses a separate volume for
- # metadata. It has better performance, especially when more data
- # is used. It also supports full snapshots.
- #
- sparse_segtype_default = "thin"
-
- # Configuration option global/lvdisplay_shows_full_device_path.
- # Enable this to reinstate the previous lvdisplay name format.
- # The default format for displaying LV names in lvdisplay was changed
- # in version 2.02.89 to show the LV name and path separately.
- # Previously this was always shown as /dev/vgname/lvname even when that
- # was never a valid path in the /dev filesystem.
- # This configuration option has an automatic default value.
- # lvdisplay_shows_full_device_path = 0
-
- # Configuration option global/use_lvmetad.
- # Use lvmetad to cache metadata and reduce disk scanning.
- # When enabled (and running), lvmetad provides LVM commands with VG
- # metadata and PV state. LVM commands then avoid reading this
- # information from disks which can be slow. When disabled (or not
- # running), LVM commands fall back to scanning disks to obtain VG
- # metadata. lvmetad is kept updated via udev rules which must be set
- # up for LVM to work correctly. (The udev rules should be installed
- # by default.) Without a proper udev setup, changes in the system's
- # block device configuration will be unknown to LVM, and ignored
- # until a manual 'pvscan --cache' is run. If lvmetad was running
- # while use_lvmetad was disabled, it must be stopped, use_lvmetad
- # enabled, and then started. When using lvmetad, LV activation is
- # switched to an automatic, event-based mode. In this mode, LVs are
- # activated based on incoming udev events that inform lvmetad when
- # PVs appear on the system. When a VG is complete (all PVs present),
- # it is auto-activated. The auto_activation_volume_list setting
- # controls which LVs are auto-activated (all by default.)
- # When lvmetad is updated (automatically by udev events, or directly
- # by pvscan --cache), devices/filter is ignored and all devices are
- # scanned by default. lvmetad always keeps unfiltered information
- # which is provided to LVM commands. Each LVM command then filters
- # based on devices/filter. This does not apply to other, non-regexp,
- # filtering settings: component filters such as multipath and MD
- # are checked during pvscan --cache. To filter a device and prevent
- # scanning from the LVM system entirely, including lvmetad, use
- # devices/global_filter.
- use_lvmetad = 1
-
- # Configuration option global/use_lvmlockd.
- # Use lvmlockd for locking among hosts using LVM on shared storage.
- # See lvmlockd(8) for more information.
- use_lvmlockd = 0
-
- # Configuration option global/lvmlockd_lock_retries.
- # Retry lvmlockd lock requests this many times.
- # This configuration option has an automatic default value.
- # lvmlockd_lock_retries = 3
-
- # Configuration option global/sanlock_lv_extend.
- # Size in MiB to extend the internal LV holding sanlock locks.
- # The internal LV holds locks for each LV in the VG, and after enough
- # LVs have been created, the internal LV needs to be extended. lvcreate
- # will automatically extend the internal LV when needed by the amount
- # specified here. Setting this to 0 disables the automatic extension
- # and can cause lvcreate to fail.
- # This configuration option has an automatic default value.
- # sanlock_lv_extend = 256
-
- # Configuration option global/thin_check_executable.
- # The full path to the thin_check command.
- # LVM uses this command to check that a thin metadata device is in a
- # usable state. When a thin pool is activated and after it is
- # deactivated, this command is run. Activation will only proceed if
- # the command has an exit status of 0. Set to "" to skip this check.
- # (Not recommended.) Also see thin_check_options.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # thin_check_executable = "/usr/sbin/thin_check"
-
- # Configuration option global/thin_dump_executable.
- # The full path to the thin_dump command.
- # LVM uses this command to dump thin pool metadata.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # thin_dump_executable = "/usr/sbin/thin_dump"
-
- # Configuration option global/thin_repair_executable.
- # The full path to the thin_repair command.
- # LVM uses this command to repair a thin metadata device if it is in
- # an unusable state. Also see thin_repair_options.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # thin_repair_executable = "/usr/sbin/thin_repair"
-
- # Configuration option global/thin_check_options.
- # List of options passed to the thin_check command.
- # With thin_check version 2.1 or newer you can add the option
- # --ignore-non-fatal-errors to let it pass through ignorable errors
- # and fix them later. With thin_check version 3.2 or newer you should
- # include the option --clear-needs-check-flag.
- # This configuration option has an automatic default value.
- # thin_check_options = [ "-q", "--clear-needs-check-flag" ]
-
- # Configuration option global/thin_repair_options.
- # List of options passed to the thin_repair command.
- # This configuration option has an automatic default value.
- # thin_repair_options = [ "" ]
-
- # Configuration option global/thin_disabled_features.
- # Features to not use in the thin driver.
- # This can be helpful for testing, or to avoid using a feature that is
- # causing problems. Features include: block_size, discards,
- # discards_non_power_2, external_origin, metadata_resize,
- # external_origin_extend, error_if_no_space.
- #
- # Example
- # thin_disabled_features = [ "discards", "block_size" ]
- #
- # This configuration option does not have a default value defined.
-
- # Configuration option global/cache_disabled_features.
- # Features to not use in the cache driver.
- # This can be helpful for testing, or to avoid using a feature that is
- # causing problems. Features include: policy_mq, policy_smq.
- #
- # Example
- # cache_disabled_features = [ "policy_smq" ]
- #
- # This configuration option does not have a default value defined.
-
- # Configuration option global/cache_check_executable.
- # The full path to the cache_check command.
- # LVM uses this command to check that a cache metadata device is in a
- # usable state. When a cached LV is activated and after it is
- # deactivated, this command is run. Activation will only proceed if the
- # command has an exit status of 0. Set to "" to skip this check.
- # (Not recommended.) Also see cache_check_options.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # cache_check_executable = "/usr/sbin/cache_check"
-
- # Configuration option global/cache_dump_executable.
- # The full path to the cache_dump command.
- # LVM uses this command to dump cache pool metadata.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # cache_dump_executable = "/usr/sbin/cache_dump"
-
- # Configuration option global/cache_repair_executable.
- # The full path to the cache_repair command.
- # LVM uses this command to repair a cache metadata device if it is in
- # an unusable state. Also see cache_repair_options.
- # (See package device-mapper-persistent-data or thin-provisioning-tools)
- # This configuration option has an automatic default value.
- # cache_repair_executable = "/usr/sbin/cache_repair"
-
- # Configuration option global/cache_check_options.
- # List of options passed to the cache_check command.
- # With cache_check version 5.0 or newer you should include the option
- # --clear-needs-check-flag.
- # This configuration option has an automatic default value.
- # cache_check_options = [ "-q", "--clear-needs-check-flag" ]
-
- # Configuration option global/cache_repair_options.
- # List of options passed to the cache_repair command.
- # This configuration option has an automatic default value.
- # cache_repair_options = [ "" ]
-
- # Configuration option global/system_id_source.
- # The method LVM uses to set the local system ID.
- # Volume Groups can also be given a system ID (by vgcreate, vgchange,
- # or vgimport.) A VG on shared storage devices is accessible only to
- # the host with a matching system ID. See 'man lvmsystemid' for
- # information on limitations and correct usage.
- #
- # Accepted values:
- # none
- # The host has no system ID.
- # lvmlocal
- # Obtain the system ID from the system_id setting in the 'local'
- # section of an lvm configuration file, e.g. lvmlocal.conf.
- # uname
- # Set the system ID from the hostname (uname) of the system.
- # System IDs beginning localhost are not permitted.
- # machineid
- # Use the contents of the machine-id file to set the system ID.
- # Some systems create this file at installation time.
- # See 'man machine-id' and global/etc.
- # file
- # Use the contents of another file (system_id_file) to set the
- # system ID.
- #
- system_id_source = "none"
-
- # Configuration option global/system_id_file.
- # The full path to the file containing a system ID.
- # This is used when system_id_source is set to 'file'.
- # Comments starting with the character # are ignored.
- # This configuration option does not have a default value defined.
-
- # Configuration option global/use_lvmpolld.
- # Use lvmpolld to supervise long running LVM commands.
- # When enabled, control of long running LVM commands is transferred
- # from the original LVM command to the lvmpolld daemon. This allows
- # the operation to continue independent of the original LVM command.
- # After lvmpolld takes over, the LVM command displays the progress
- # of the ongoing operation. lvmpolld itself runs LVM commands to
- # manage the progress of ongoing operations. lvmpolld can be used as
- # a native systemd service, which allows it to be started on demand,
- # and to use its own control group. When this option is disabled, LVM
- # commands will supervise long running operations by forking themselves.
- use_lvmpolld = 1
- }
-
- # Configuration section activation.
- activation {
-
-
-
-
-
-
- checks = 0
-
-
-
-
-
-
-
-
-
-
- udev_sync = 1
-
-
-
-
-
-
- udev_rules = 1
-
-
-
-
-
-
- verify_udev_operations = 0
-
-
-
-
-
-
- retry_deactivation = 1
-
-
-
-
-
-
-
-
-
- missing_stripe_filler = "error"
-
-
-
-
-
-
- use_linear_target = 1
-
-
-
-
- reserved_stack = 64
-
-
-
-
- reserved_memory = 8192
-
-
-
-
-
- process_priority = -18
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- raid_region_size = 512
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- readahead = "auto"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- raid_fault_policy = "warn"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- mirror_image_fault_policy = "remove"
-
-
-
-
-
- mirror_log_fault_policy = "allocate"
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- snapshot_autoextend_threshold = 100
-
-
-
-
-
-
-
-
-
-
-
-
- snapshot_autoextend_percent = 20
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- thin_pool_autoextend_threshold = 100
-
-
-
-
-
-
-
-
-
-
-
-
- thin_pool_autoextend_percent = 20
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- use_mlockall = 0
-
-
-
-
-
- monitoring = 1
-
-
-
-
-
-
-
-
- polling_interval = 15
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- activation_mode = "degraded"
-
-
-
-
-
-
-
-
-
-
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- dmeventd {
-
-
-
-
-
-
-
- mirror_library = "libdevmapper-event-lvm2mirror.so"
-
-
-
-
-
-
-
-
-
-
- snapshot_library = "libdevmapper-event-lvm2snapshot.so"
-
-
-
-
-
-
- thin_library = "libdevmapper-event-lvm2thin.so"
-
-
-
-
-
- }
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
|