1 # This is an example configuration file for the LVM2 system.
2 # It contains the default settings that would be used if there was no
3 # /etc/lvm/lvm.conf file.
5 # Refer to 'man lvm.conf' for further information including the file layout.
7 # Refer to 'man lvm.conf' for information about how settings configured in
8 # this file are combined with built-in values and command line options to
9 # arrive at the final values used by LVM.
11 # Refer to 'man lvmconfig' for information about displaying the built-in
12 # and configured values used by LVM.
14 # If a default value is set in this file (not commented out), then a
15 # new version of LVM using this file will continue using that value,
16 # even if the new version of LVM changes the built-in default value.
18 # To put this file in a different directory and override /etc/lvm set
19 # the environment variable LVM_SYSTEM_DIR before running the tools.
21 # N.B. Take care that each setting only appears once if uncommenting
22 # example settings in this file.
25 # Configuration section config.
26 # How LVM configuration settings are handled.
29 # Configuration option config/checks.
30 # If enabled, any LVM configuration mismatch is reported.
31 # This implies checking that the configuration key is understood by
32 # LVM and that the value of the key is the proper type. If disabled,
33 # any configuration mismatch is ignored and the default value is used
34 # without any warning (a message about the configuration key not being
35 # found is issued in verbose mode only).
38 # Configuration option config/abort_on_errors.
39 # Abort the LVM process if a configuration mismatch is found.
42 # Configuration option config/profile_dir.
43 # Directory where LVM looks for configuration profiles.
44 profile_dir = "/etc/lvm/profile"
47 # Configuration section devices.
48 # How LVM uses block devices.
51 # Configuration option devices/dir.
52 # Directory in which to create volume group device nodes.
53 # Commands also accept this as a prefix on volume group names.
54 # This configuration option is advanced.
57 # Configuration option devices/scan.
58 # Directories containing device nodes to use with LVM.
59 # This configuration option is advanced.
62 # Configuration option devices/obtain_device_list_from_udev.
63 # Obtain the list of available devices from udev.
64 # This avoids opening or using any inapplicable non-block devices or
65 # subdirectories found in the udev directory. Any device node or
66 # symlink not managed by udev in the udev directory is ignored. This
67 # setting applies only to the udev-managed device directory; other
68 # directories will be scanned fully. LVM needs to be compiled with
69 # udev support for this setting to apply.
70 obtain_device_list_from_udev = 1
72 # Configuration option devices/external_device_info_source.
73 # Select an external device information source.
74 # Some information may already be available in the system and LVM can
75 # use this information to determine the exact type or use of devices it
76 # processes. Using an existing external device information source can
77 # speed up device processing as LVM does not need to run its own native
78 # routines to acquire this information. For example, this information
79 # is used to drive LVM filtering like MD component detection, multipath
80 # component detection, partition detection and others.
84 # No external device information source is used.
86 # Reuse existing udev database records. Applicable only if LVM is
87 # compiled with udev support.
89 external_device_info_source = "none"
91 # Configuration option devices/preferred_names.
92 # Select which path name to display for a block device.
93 # If multiple path names exist for a block device, and LVM needs to
94 # display a name for the device, the path names are matched against
95 # each item in this list of regular expressions. The first match is
96 # used. Try to avoid using undescriptive /dev/dm-N names, if present.
97 # If no preferred name matches, or if preferred_names are not defined,
98 # the following built-in preferences are applied in order until one
99 # produces a preferred name:
100 # Prefer names with path prefixes in the order of:
101 # /dev/mapper, /dev/disk, /dev/dm-*, /dev/block.
102 # Prefer the name with the least number of slashes.
103 # Prefer a name that is a symlink.
104 # Prefer the path with least value in lexicographical order.
107 # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
109 # This configuration option does not have a default value defined.
110 preferred_names = [ ]
112 # Configuration option devices/filter.
113 # Limit the block devices that are used by LVM commands.
114 # This is a list of regular expressions used to accept or reject block
115 # device path names. Each regex is delimited by a vertical bar '|'
116 # (or any character) and is preceded by 'a' to accept the path, or
117 # by 'r' to reject the path. The first regex in the list to match the
118 # path is used, producing the 'a' or 'r' result for the device.
119 # When multiple path names exist for a block device, if any path name
120 # matches an 'a' pattern before an 'r' pattern, then the device is
121 # accepted. If all the path names match an 'r' pattern first, then the
122 # device is rejected. Unmatching path names do not affect the accept
123 # or reject decision. If no path names for a device match a pattern,
124 # then the device is accepted. Be careful mixing 'a' and 'r' patterns,
125 # as the combination might produce unexpected results (test changes.)
126 # Run vgscan after changing the filter to regenerate the cache.
129 # Accept every block device:
130 # filter = [ "a|.*/|" ]
131 # Reject the cdrom drive:
132 # filter = [ "r|/dev/cdrom|" ]
133 # Work with just loopback devices, e.g. for testing:
134 # filter = [ "a|loop|", "r|.*|" ]
135 # Accept all loop devices and ide drives except hdc:
136 # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
137 # Use anchors to be very specific:
138 # filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
140 # This configuration option has an automatic default value.
141 # filter = [ "a|.*/|" ]
142 filter = [ "a|^/dev/md[0-9]*$|", "r/.*/" ]
144 # Configuration option devices/global_filter.
145 # Limit the block devices that are used by LVM system components.
146 # Because devices/filter may be overridden from the command line, it is
147 # not suitable for system-wide device filtering, e.g. udev.
148 # Use global_filter to hide devices from these LVM system components.
149 # The syntax is the same as devices/filter. Devices rejected by
150 # global_filter are not opened by LVM.
151 # This configuration option has an automatic default value.
152 # global_filter = [ "a|.*/|" ]
153 global_filter = [ "a|^/dev/md[0-9]*$|", "r/.*/" ]
155 # Configuration option devices/types.
156 # List of additional acceptable block device types.
157 # These are of device type names from /proc/devices, followed by the
158 # maximum number of partitions.
161 # types = [ "fd", 16 ]
163 # This configuration option is advanced.
164 # This configuration option does not have a default value defined.
166 # Configuration option devices/sysfs_scan.
167 # Restrict device scanning to block devices appearing in sysfs.
168 # This is a quick way of filtering out block devices that are not
169 # present on the system. sysfs must be part of the kernel and mounted.)
172 # Configuration option devices/scan_lvs.
173 # Scan LVM LVs for layered PVs.
176 # Configuration option devices/multipath_component_detection.
177 # Ignore devices that are components of DM multipath devices.
178 multipath_component_detection = 1
180 # Configuration option devices/md_component_detection.
181 # Ignore devices that are components of software RAID (md) devices.
182 md_component_detection = 1
184 # Configuration option devices/fw_raid_component_detection.
185 # Ignore devices that are components of firmware RAID devices.
186 # LVM must use an external_device_info_source other than none for this
187 # detection to execute.
188 fw_raid_component_detection = 0
190 # Configuration option devices/md_chunk_alignment.
191 # Align the start of a PV data area with md device's stripe-width.
192 # This applies if a PV is placed directly on an md device.
193 # default_data_alignment will be overriden if it is not aligned
194 # with the value detected for this setting.
195 # This setting is overriden by data_alignment_detection,
196 # data_alignment, and the --dataalignment option.
197 md_chunk_alignment = 1
199 # Configuration option devices/default_data_alignment.
200 # Align the start of a PV data area with this number of MiB.
201 # Set to 1 for 1MiB, 2 for 2MiB, etc. Set to 0 to disable.
202 # This setting is overriden by data_alignment and the --dataalignment
204 # This configuration option has an automatic default value.
205 # default_data_alignment = 1
207 # Configuration option devices/data_alignment_detection.
208 # Align the start of a PV data area with sysfs io properties.
209 # The start of a PV data area will be a multiple of minimum_io_size or
210 # optimal_io_size exposed in sysfs. minimum_io_size is the smallest
211 # request the device can perform without incurring a read-modify-write
212 # penalty, e.g. MD chunk size. optimal_io_size is the device's
213 # preferred unit of receiving I/O, e.g. MD stripe width.
214 # minimum_io_size is used if optimal_io_size is undefined (0).
215 # If md_chunk_alignment is enabled, that detects the optimal_io_size.
216 # default_data_alignment and md_chunk_alignment will be overriden
217 # if they are not aligned with the value detected for this setting.
218 # This setting is overriden by data_alignment and the --dataalignment
220 data_alignment_detection = 1
222 # Configuration option devices/data_alignment.
223 # Align the start of a PV data area with this number of KiB.
224 # When non-zero, this setting overrides default_data_alignment.
225 # Set to 0 to disable, in which case default_data_alignment
226 # is used to align the first PE in units of MiB.
227 # This setting is overriden by the --dataalignment option.
230 # Configuration option devices/data_alignment_offset_detection.
231 # Shift the start of an aligned PV data area based on sysfs information.
232 # After a PV data area is aligned, it will be shifted by the
233 # alignment_offset exposed in sysfs. This offset is often 0, but may
234 # be non-zero. Certain 4KiB sector drives that compensate for windows
235 # partitioning will have an alignment_offset of 3584 bytes (sector 7
236 # is the lowest aligned logical block, the 4KiB sectors start at
237 # LBA -1, and consequently sector 63 is aligned on a 4KiB boundary).
238 # This setting is overriden by the --dataalignmentoffset option.
239 data_alignment_offset_detection = 1
241 # Configuration option devices/ignore_suspended_devices.
242 # Ignore DM devices that have I/O suspended while scanning devices.
243 # Otherwise, LVM waits for a suspended device to become accessible.
244 # This should only be needed in recovery situations.
245 ignore_suspended_devices = 0
247 # Configuration option devices/ignore_lvm_mirrors.
248 # Do not scan 'mirror' LVs to avoid possible deadlocks.
249 # This avoids possible deadlocks when using the 'mirror' segment type.
250 # This setting determines whether LVs using the 'mirror' segment type
251 # are scanned for LVM labels. This affects the ability of mirrors to
252 # be used as physical volumes. If this setting is enabled, it is
253 # impossible to create VGs on top of mirror LVs, i.e. to stack VGs on
254 # mirror LVs. If this setting is disabled, allowing mirror LVs to be
255 # scanned, it may cause LVM processes and I/O to the mirror to become
256 # blocked. This is due to the way that the mirror segment type handles
257 # failures. In order for the hang to occur, an LVM command must be run
258 # just after a failure and before the automatic LVM repair process
259 # takes place, or there must be failures in multiple mirrors in the
260 # same VG at the same time with write failures occurring moments before
261 # a scan of the mirror's labels. The 'mirror' scanning problems do not
262 # apply to LVM RAID types like 'raid1' which handle failures in a
263 # different way, making them a better choice for VG stacking.
264 ignore_lvm_mirrors = 1
266 # Configuration option devices/require_restorefile_with_uuid.
267 # Allow use of pvcreate --uuid without requiring --restorefile.
268 require_restorefile_with_uuid = 1
270 # Configuration option devices/pv_min_size.
271 # Minimum size in KiB of block devices which can be used as PVs.
272 # In a clustered environment all nodes must use the same value.
273 # Any value smaller than 512KiB is ignored. The previous built-in
277 # Configuration option devices/issue_discards.
278 # Issue discards to PVs that are no longer used by an LV.
279 # Discards are sent to an LV's underlying physical volumes when the LV
280 # is no longer using the physical volumes' space, e.g. lvremove,
281 # lvreduce. Discards inform the storage that a region is no longer
282 # used. Storage that supports discards advertise the protocol-specific
283 # way discards should be issued by the kernel (TRIM, UNMAP, or
284 # WRITE SAME with UNMAP bit set). Not all storage will support or
285 # benefit from discards, but SSDs and thinly provisioned LUNs
286 # generally do. If enabled, discards will only be issued if both the
287 # storage and kernel provide support.
290 # Configuration option devices/allow_changes_with_duplicate_pvs.
291 # Allow VG modification while a PV appears on multiple devices.
292 # When a PV appears on multiple devices, LVM attempts to choose the
293 # best device to use for the PV. If the devices represent the same
294 # underlying storage, the choice has minimal consequence. If the
295 # devices represent different underlying storage, the wrong choice
296 # can result in data loss if the VG is modified. Disabling this
297 # setting is the safest option because it prevents modifying a VG
298 # or activating LVs in it while a PV appears on multiple devices.
299 # Enabling this setting allows the VG to be used as usual even with
301 allow_changes_with_duplicate_pvs = 0
304 # Configuration section allocation.
305 # How LVM selects space and applies properties to LVs.
308 # Configuration option allocation/cling_tag_list.
309 # Advise LVM which PVs to use when searching for new space.
310 # When searching for free space to extend an LV, the 'cling' allocation
311 # policy will choose space on the same PVs as the last segment of the
312 # existing LV. If there is insufficient space and a list of tags is
313 # defined here, it will check whether any of them are attached to the
314 # PVs concerned and then seek to match those PV tags between existing
315 # extents and new extents.
318 # Use the special tag "@*" as a wildcard to match any PV tag:
319 # cling_tag_list = [ "@*" ]
320 # LVs are mirrored between two sites within a single VG, and
321 # PVs are tagged with either @site1 or @site2 to indicate where
323 # cling_tag_list = [ "@site1", "@site2" ]
325 # This configuration option does not have a default value defined.
327 # Configuration option allocation/maximise_cling.
328 # Use a previous allocation algorithm.
329 # Changes made in version 2.02.85 extended the reach of the 'cling'
330 # policies to detect more situations where data can be grouped onto
331 # the same disks. This setting can be used to disable the changes
332 # and revert to the previous algorithm.
335 # Configuration option allocation/use_blkid_wiping.
336 # Use blkid to detect and erase existing signatures on new PVs and LVs.
337 # The blkid library can detect more signatures than the native LVM
338 # detection code, but may take longer. LVM needs to be compiled with
339 # blkid wiping support for this setting to apply. LVM native detection
340 # code is currently able to recognize: MD device signatures,
341 # swap signature, and LUKS signatures. To see the list of signatures
342 # recognized by blkid, check the output of the 'blkid -k' command.
345 # Configuration option allocation/wipe_signatures_when_zeroing_new_lvs.
346 # Look for and erase any signatures while zeroing a new LV.
347 # The --wipesignatures option overrides this setting.
348 # Zeroing is controlled by the -Z/--zero option, and if not specified,
349 # zeroing is used by default if possible. Zeroing simply overwrites the
350 # first 4KiB of a new LV with zeroes and does no signature detection or
351 # wiping. Signature wiping goes beyond zeroing and detects exact types
352 # and positions of signatures within the whole LV. It provides a
353 # cleaner LV after creation as all known signatures are wiped. The LV
354 # is not claimed incorrectly by other tools because of old signatures
355 # from previous use. The number of signatures that LVM can detect
356 # depends on the detection code that is selected (see
357 # use_blkid_wiping.) Wiping each detected signature must be confirmed.
358 # When this setting is disabled, signatures on new LVs are not detected
359 # or erased unless the --wipesignatures option is used directly.
360 wipe_signatures_when_zeroing_new_lvs = 1
362 # Configuration option allocation/mirror_logs_require_separate_pvs.
363 # Mirror logs and images will always use different PVs.
364 # The default setting changed in version 2.02.85.
365 mirror_logs_require_separate_pvs = 0
367 # Configuration option allocation/raid_stripe_all_devices.
368 # Stripe across all PVs when RAID stripes are not specified.
369 # If enabled, all PVs in the VG or on the command line are used for
370 # raid0/4/5/6/10 when the command does not specify the number of
372 # This was the default behaviour until release 2.02.162.
373 # This configuration option has an automatic default value.
374 # raid_stripe_all_devices = 0
376 # Configuration option allocation/cache_pool_metadata_require_separate_pvs.
377 # Cache pool metadata and data will always use different PVs.
378 cache_pool_metadata_require_separate_pvs = 0
380 # Configuration option allocation/cache_metadata_format.
381 # Sets default metadata format for new cache.
384 # 0 Automatically detected best available format
386 # 2 Improved 2nd. generation format
388 # This configuration option has an automatic default value.
389 # cache_metadata_format = 0
391 # Configuration option allocation/cache_mode.
392 # The default cache mode used for new cache.
396 # Data blocks are immediately written from the cache to disk.
398 # Data blocks are written from the cache back to disk after some
399 # delay to improve performance.
401 # This setting replaces allocation/cache_pool_cachemode.
402 # This configuration option has an automatic default value.
403 # cache_mode = "writethrough"
405 # Configuration option allocation/cache_policy.
406 # The default cache policy used for new cache volume.
407 # Since kernel 4.2 the default policy is smq (Stochastic multiqueue),
408 # otherwise the older mq (Multiqueue) policy is selected.
409 # This configuration option does not have a default value defined.
411 # Configuration section allocation/cache_settings.
412 # Settings for the cache policy.
413 # See documentation for individual cache policies for more info.
414 # This configuration section has an automatic default value.
418 # Configuration option allocation/cache_pool_chunk_size.
419 # The minimal chunk size in KiB for cache pool volumes.
420 # Using a chunk_size that is too large can result in wasteful use of
421 # the cache, where small reads and writes can cause large sections of
422 # an LV to be mapped into the cache. However, choosing a chunk_size
423 # that is too small can result in more overhead trying to manage the
424 # numerous chunks that become mapped into the cache. The former is
425 # more of a problem than the latter in most cases, so the default is
426 # on the smaller end of the spectrum. Supported values range from
427 # 32KiB to 1GiB in multiples of 32.
428 # This configuration option does not have a default value defined.
430 # Configuration option allocation/cache_pool_max_chunks.
431 # The maximum number of chunks in a cache pool.
432 # For cache target v1.9 the recommended maximumm is 1000000 chunks.
433 # Using cache pool with more chunks may degrade cache performance.
434 # This configuration option does not have a default value defined.
436 # Configuration option allocation/thin_pool_metadata_require_separate_pvs.
437 # Thin pool metdata and data will always use different PVs.
438 thin_pool_metadata_require_separate_pvs = 0
440 # Configuration option allocation/thin_pool_zero.
441 # Thin pool data chunks are zeroed before they are first used.
442 # Zeroing with a larger thin pool chunk size reduces performance.
443 # This configuration option has an automatic default value.
446 # Configuration option allocation/thin_pool_discards.
447 # The discards behaviour of thin pool volumes.
454 # This configuration option has an automatic default value.
455 # thin_pool_discards = "passdown"
457 # Configuration option allocation/thin_pool_chunk_size_policy.
458 # The chunk size calculation policy for thin pool volumes.
462 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
463 # the chunk size based on estimation and device hints exposed in
464 # sysfs - the minimum_io_size. The chunk size is always at least
467 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
468 # the chunk size for performance based on device hints exposed in
469 # sysfs - the optimal_io_size. The chunk size is always at least
472 # This configuration option has an automatic default value.
473 # thin_pool_chunk_size_policy = "generic"
475 # Configuration option allocation/thin_pool_chunk_size.
476 # The minimal chunk size in KiB for thin pool volumes.
477 # Larger chunk sizes may improve performance for plain thin volumes,
478 # however using them for snapshot volumes is less efficient, as it
479 # consumes more space and takes extra time for copying. When unset,
480 # lvm tries to estimate chunk size starting from 64KiB. Supported
481 # values are in the range 64KiB to 1GiB.
482 # This configuration option does not have a default value defined.
484 # Configuration option allocation/physical_extent_size.
485 # Default physical extent size in KiB to use for new VGs.
486 # This configuration option has an automatic default value.
487 # physical_extent_size = 4096
489 # Configuration option allocation/vdo_use_compression.
490 # Enables or disables compression when creating a VDO volume.
491 # Compression may be disabled if necessary to maximize performance
492 # or to speed processing of data that is unlikely to compress.
493 # This configuration option has an automatic default value.
494 # vdo_use_compression = 1
496 # Configuration option allocation/vdo_use_deduplication.
497 # Enables or disables deduplication when creating a VDO volume.
498 # Deduplication may be disabled in instances where data is not expected
499 # to have good deduplication rates but compression is still desired.
500 # This configuration option has an automatic default value.
501 # vdo_use_deduplication = 1
503 # Configuration option allocation/vdo_emulate_512_sectors.
504 # Specifies that the VDO volume is to emulate a 512 byte block device.
505 # This configuration option has an automatic default value.
506 # vdo_emulate_512_sectors = 0
508 # Configuration option allocation/vdo_block_map_cache_size_mb.
509 # Specifies the amount of memory in MiB allocated for caching block map
510 # pages for VDO volume. The value must be a multiple of 4096 and must be
511 # at least 128MiB and less than 16TiB. The cache must be at least 16MiB
512 # per logical thread. Note that there is a memory overhead of 15%.
513 # This configuration option has an automatic default value.
514 # vdo_block_map_cache_size_mb = 128
516 # Configuration option allocation/vdo_block_map_period.
517 # Tunes the quantity of block map updates that can accumulate
518 # before cache pages are flushed to disk. The value must be
519 # at least 1 and less then 16380.
520 # A lower value means shorter recovery time but lower performance.
521 # This configuration option has an automatic default value.
522 # vdo_block_map_period = 16380
524 # Configuration option allocation/vdo_check_point_frequency.
525 # The default check point frequency for VDO volume.
526 # This configuration option has an automatic default value.
527 # vdo_check_point_frequency = 0
529 # Configuration option allocation/vdo_use_sparse_index.
530 # Enables sparse indexing for VDO volume.
531 # This configuration option has an automatic default value.
532 # vdo_use_sparse_index = 0
534 # Configuration option allocation/vdo_index_memory_size_mb.
535 # Specifies the amount of index memory in MiB for VDO volume.
536 # The value must be at least 256MiB and at most 1TiB.
537 # This configuration option has an automatic default value.
538 # vdo_index_memory_size_mb = 256
540 # Configuration option allocation/vdo_use_read_cache.
541 # Enables or disables the read cache within the VDO volume.
542 # The cache should be enabled if write workloads are expected
543 # to have high levels of deduplication, or for read intensive
544 # workloads of highly compressible data.
545 # This configuration option has an automatic default value.
546 # vdo_use_read_cache = 0
548 # Configuration option allocation/vdo_read_cache_size_mb.
549 # Specifies the extra VDO volume read cache size in MiB.
550 # This space is in addition to a system-defined minimum.
551 # The value must be less then 16TiB and 1.12 MiB of memory
552 # will be used per MiB of read cache specified, per bio thread.
553 # This configuration option has an automatic default value.
554 # vdo_read_cache_size_mb = 0
556 # Configuration option allocation/vdo_slab_size_mb.
557 # Specifies the size in MiB of the increment by which a VDO is grown.
558 # Using a smaller size constrains the total maximum physical size
559 # that can be accommodated. Must be a power of two between 128MiB and 32GiB.
560 # This configuration option has an automatic default value.
561 # vdo_slab_size_mb = 2048
563 # Configuration option allocation/vdo_ack_threads.
564 # Specifies the number of threads to use for acknowledging
565 # completion of requested VDO I/O operations.
566 # The value must be at in range [0..100].
567 # This configuration option has an automatic default value.
568 # vdo_ack_threads = 1
570 # Configuration option allocation/vdo_bio_threads.
571 # Specifies the number of threads to use for submitting I/O
572 # operations to the storage device of VDO volume.
573 # The value must be in range [1..100]
574 # Each additional thread after the first will use an additional 18MiB of RAM,
575 # plus 1.12 MiB of RAM per megabyte of configured read cache size.
576 # This configuration option has an automatic default value.
577 # vdo_bio_threads = 1
579 # Configuration option allocation/vdo_bio_rotation.
580 # Specifies the number of I/O operations to enqueue for each bio-submission
581 # thread before directing work to the next. The value must be in range [1..1024].
582 # This configuration option has an automatic default value.
583 # vdo_bio_rotation = 64
585 # Configuration option allocation/vdo_cpu_threads.
586 # Specifies the number of threads to use for CPU-intensive work such as
587 # hashing or compression for VDO volume. The value must be in range [1..100]
588 # This configuration option has an automatic default value.
589 # vdo_cpu_threads = 2
591 # Configuration option allocation/vdo_hash_zone_threads.
592 # Specifies the number of threads across which to subdivide parts of the VDO
593 # processing based on the hash value computed from the block data.
594 # The value must be at in range [0..100].
595 # vdo_hash_zone_threads, vdo_logical_threads and vdo_physical_threads must be
596 # either all zero or all non-zero.
597 # This configuration option has an automatic default value.
598 # vdo_hash_zone_threads = 1
600 # Configuration option allocation/vdo_logical_threads.
601 # Specifies the number of threads across which to subdivide parts of the VDO
602 # processing based on the hash value computed from the block data.
603 # A logical thread count of 9 or more will require explicitly specifying
604 # a sufficiently large block map cache size, as well.
605 # The value must be in range [0..100].
606 # vdo_hash_zone_threads, vdo_logical_threads and vdo_physical_threads must be
607 # either all zero or all non-zero.
608 # This configuration option has an automatic default value.
609 # vdo_logical_threads = 1
611 # Configuration option allocation/vdo_physical_threads.
612 # Specifies the number of threads across which to subdivide parts of the VDO
613 # processing based on physical block addresses.
614 # Each additional thread after the first will use an additional 10MiB of RAM.
615 # The value must be in range [0..16].
616 # vdo_hash_zone_threads, vdo_logical_threads and vdo_physical_threads must be
617 # either all zero or all non-zero.
618 # This configuration option has an automatic default value.
619 # vdo_physical_threads = 1
621 # Configuration option allocation/vdo_write_policy.
622 # Specifies the write policy:
623 # auto - VDO will check the storage device and determine whether it supports flushes.
624 # If it does, VDO will run in async mode, otherwise it will run in sync mode.
625 # sync - Writes are acknowledged only after data is stably written.
626 # This policy is not supported if the underlying storage is not also synchronous.
627 # async - Writes are acknowledged after data has been cached for writing to stable storage.
628 # Data which has not been flushed is not guaranteed to persist in this mode.
629 # This configuration option has an automatic default value.
630 # vdo_write_policy = "auto"
633 # Configuration section log.
634 # How LVM log information is reported.
637 # Configuration option log/report_command_log.
638 # Enable or disable LVM log reporting.
639 # If enabled, LVM will collect a log of operations, messages,
640 # per-object return codes with object identification and associated
641 # error numbers (errnos) during LVM command processing. Then the
642 # log is either reported solely or in addition to any existing
643 # reports, depending on LVM command used. If it is a reporting command
644 # (e.g. pvs, vgs, lvs, lvm fullreport), then the log is reported in
645 # addition to any existing reports. Otherwise, there's only log report
646 # on output. For all applicable LVM commands, you can request that
647 # the output has only log report by using --logonly command line
648 # option. Use log/command_log_cols and log/command_log_sort settings
649 # to define fields to display and sort fields for the log report.
650 # You can also use log/command_log_selection to define selection
651 # criteria used each time the log is reported.
652 # This configuration option has an automatic default value.
653 # report_command_log = 0
655 # Configuration option log/command_log_sort.
656 # List of columns to sort by when reporting command log.
657 # See <lvm command> --logonly --configreport log -o help
658 # for the list of possible fields.
659 # This configuration option has an automatic default value.
660 # command_log_sort = "log_seq_num"
662 # Configuration option log/command_log_cols.
663 # List of columns to report when reporting command log.
664 # See <lvm command> --logonly --configreport log -o help
665 # for the list of possible fields.
666 # This configuration option has an automatic default value.
667 # command_log_cols = "log_seq_num,log_type,log_context,log_object_type,log_object_name,log_object_id,log_object_group,log_object_group_id,log_message,log_errno,log_ret_code"
669 # Configuration option log/command_log_selection.
670 # Selection criteria used when reporting command log.
671 # You can define selection criteria that are applied each
672 # time log is reported. This way, it is possible to control the
673 # amount of log that is displayed on output and you can select
674 # only parts of the log that are important for you. To define
675 # selection criteria, use fields from log report. See also
676 # <lvm command> --logonly --configreport log -S help for the
677 # list of possible fields and selection operators. You can also
678 # define selection criteria for log report on command line directly
679 # using <lvm command> --configreport log -S <selection criteria>
680 # which has precedence over log/command_log_selection setting.
681 # For more information about selection criteria in general, see
683 # This configuration option has an automatic default value.
684 # command_log_selection = "!(log_type=status && message=success)"
686 # Configuration option log/verbose.
687 # Controls the messages sent to stdout or stderr.
690 # Configuration option log/silent.
691 # Suppress all non-essential messages from stdout.
692 # This has the same effect as -qq. When enabled, the following commands
693 # still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck,
694 # pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs.
695 # Non-essential messages are shifted from log level 4 to log level 5
696 # for syslog and lvm2_log_fn purposes.
697 # Any 'yes' or 'no' questions not overridden by other arguments are
698 # suppressed and default to 'no'.
701 # Configuration option log/syslog.
702 # Send log messages through syslog.
705 # Configuration option log/file.
706 # Write error and debug log messages to a file specified here.
707 # This configuration option does not have a default value defined.
709 # Configuration option log/overwrite.
710 # Overwrite the log file each time the program is run.
713 # Configuration option log/level.
714 # The level of log messages that are sent to the log file or syslog.
715 # There are 6 syslog-like log levels currently in use: 2 to 7 inclusive.
716 # 7 is the most verbose (LOG_DEBUG).
719 # Configuration option log/indent.
720 # Indent messages according to their severity.
723 # Configuration option log/command_names.
724 # Display the command name on each line of output.
727 # Configuration option log/prefix.
728 # A prefix to use before the log message text.
729 # (After the command name, if selected).
730 # Two spaces allows you to see/grep the severity of each message.
731 # To make the messages look similar to the original LVM tools use:
732 # indent = 0, command_names = 1, prefix = " -- "
735 # Configuration option log/activation.
736 # Log messages during activation.
737 # Don't use this in low memory situations (can deadlock).
740 # Configuration option log/debug_classes.
741 # Select log messages by class.
742 # Some debugging messages are assigned to a class and only appear in
743 # debug output if the class is listed here. Classes currently
744 # available: memory, devices, io, activation, allocation,
745 # metadata, cache, locking, lvmpolld. Use "all" to see everything.
746 debug_classes = [ "memory", "devices", "io", "activation", "allocation", "metadata", "cache", "locking", "lvmpolld", "dbus" ]
749 # Configuration section backup.
750 # How LVM metadata is backed up and archived.
751 # In LVM, a 'backup' is a copy of the metadata for the current system,
752 # and an 'archive' contains old metadata configurations. They are
753 # stored in a human readable text format.
756 # Configuration option backup/backup.
757 # Maintain a backup of the current metadata configuration.
758 # Think very hard before turning this off!
761 # Configuration option backup/backup_dir.
762 # Location of the metadata backup files.
763 # Remember to back up this directory regularly!
764 backup_dir = "/etc/lvm/backup"
766 # Configuration option backup/archive.
767 # Maintain an archive of old metadata configurations.
768 # Think very hard before turning this off.
771 # Configuration option backup/archive_dir.
772 # Location of the metdata archive files.
773 # Remember to back up this directory regularly!
774 archive_dir = "/etc/lvm/archive"
776 # Configuration option backup/retain_min.
777 # Minimum number of archives to keep.
780 # Configuration option backup/retain_days.
781 # Minimum number of days to keep archive files.
785 # Configuration section shell.
786 # Settings for running LVM in shell (readline) mode.
789 # Configuration option shell/history_size.
790 # Number of lines of history to store in ~/.lvm_history.
794 # Configuration section global.
795 # Miscellaneous global LVM settings.
798 # Configuration option global/umask.
799 # The file creation mask for any files and directories created.
800 # Interpreted as octal if the first digit is zero.
803 # Configuration option global/test.
804 # No on-disk metadata changes will be made in test mode.
805 # Equivalent to having the -t option on every command.
808 # Configuration option global/units.
809 # Default value for --units argument.
812 # Configuration option global/si_unit_consistency.
813 # Distinguish between powers of 1024 and 1000 bytes.
814 # The LVM commands distinguish between powers of 1024 bytes,
815 # e.g. KiB, MiB, GiB, and powers of 1000 bytes, e.g. KB, MB, GB.
816 # If scripts depend on the old behaviour, disable this setting
817 # temporarily until they are updated.
818 si_unit_consistency = 1
820 # Configuration option global/suffix.
821 # Display unit suffix for sizes.
822 # This setting has no effect if the units are in human-readable form
823 # (global/units = "h") in which case the suffix is always displayed.
826 # Configuration option global/activation.
827 # Enable/disable communication with the kernel device-mapper.
828 # Disable to use the tools to manipulate LVM metadata without
829 # activating any logical volumes. If the device-mapper driver
830 # is not present in the kernel, disabling this should suppress
831 # the error messages.
834 # Configuration option global/segment_libraries.
835 # This configuration option does not have a default value defined.
837 # Configuration option global/proc.
838 # Location of proc filesystem.
839 # This configuration option is advanced.
842 # Configuration option global/etc.
843 # Location of /etc system configuration directory.
846 # Configuration option global/wait_for_locks.
847 # When disabled, fail if a lock request would block.
850 # Configuration option global/locking_dir.
851 # Directory to use for LVM command file locks.
852 # Local non-LV directory that holds file-based locks while commands are
853 # in progress. A directory like /tmp that may get wiped on reboot is OK.
854 locking_dir = "/run/lock/lvm"
856 # Configuration option global/prioritise_write_locks.
857 # Allow quicker VG write access during high volume read access.
858 # When there are competing read-only and read-write access requests for
859 # a volume group's metadata, instead of always granting the read-only
860 # requests immediately, delay them to allow the read-write requests to
861 # be serviced. Without this setting, write access may be stalled by a
862 # high volume of read-only requests. This option only affects
863 # locking_type 1 viz. local file-based locking.
864 prioritise_write_locks = 1
866 # Configuration option global/library_dir.
867 # Search this directory first for shared libraries.
868 # This configuration option does not have a default value defined.
870 # Configuration option global/abort_on_internal_errors.
871 # Abort a command that encounters an internal error.
872 # Treat any internal errors as fatal errors, aborting the process that
873 # encountered the internal error. Please only enable for debugging.
874 abort_on_internal_errors = 0
876 # Configuration option global/metadata_read_only.
877 # No operations that change on-disk metadata are permitted.
878 # Additionally, read-only commands that encounter metadata in need of
879 # repair will still be allowed to proceed exactly as if the repair had
880 # been performed (except for the unchanged vg_seqno). Inappropriate
881 # use could mess up your system, so seek advice first!
882 metadata_read_only = 0
884 # Configuration option global/mirror_segtype_default.
885 # The segment type used by the short mirroring option -m.
886 # The --type mirror|raid1 option overrides this setting.
890 # The original RAID1 implementation from LVM/DM. It is
891 # characterized by a flexible log solution (core, disk, mirrored),
892 # and by the necessity to block I/O while handling a failure.
893 # There is an inherent race in the dmeventd failure handling logic
894 # with snapshots of devices using this type of RAID1 that in the
895 # worst case could cause a deadlock. (Also see
896 # devices/ignore_lvm_mirrors.)
898 # This is a newer RAID1 implementation using the MD RAID1
899 # personality through device-mapper. It is characterized by a
900 # lack of log options. (A log is always allocated for every
901 # device and they are placed on the same device as the image,
902 # so no separate devices are required.) This mirror
903 # implementation does not require I/O to be blocked while
904 # handling a failure. This mirror implementation is not
905 # cluster-aware and cannot be used in a shared (active/active)
906 # fashion in a cluster.
908 mirror_segtype_default = "raid1"
910 # Configuration option global/raid10_segtype_default.
911 # The segment type used by the -i -m combination.
912 # The --type raid10|mirror option overrides this setting.
913 # The --stripes/-i and --mirrors/-m options can both be specified
914 # during the creation of a logical volume to use both striping and
915 # mirroring for the LV. There are two different implementations.
919 # LVM uses MD's RAID10 personality through DM. This is the
922 # LVM layers the 'mirror' and 'stripe' segment types. The layering
923 # is done by creating a mirror LV on top of striped sub-LVs,
924 # effectively creating a RAID 0+1 array. The layering is suboptimal
925 # in terms of providing redundancy and performance.
927 raid10_segtype_default = "raid10"
929 # Configuration option global/sparse_segtype_default.
930 # The segment type used by the -V -L combination.
931 # The --type snapshot|thin option overrides this setting.
932 # The combination of -V and -L options creates a sparse LV. There are
933 # two different implementations.
937 # The original snapshot implementation from LVM/DM. It uses an old
938 # snapshot that mixes data and metadata within a single COW
939 # storage volume and performs poorly when the size of stored data
940 # passes hundreds of MB.
942 # A newer implementation that uses thin provisioning. It has a
943 # bigger minimal chunk size (64KiB) and uses a separate volume for
944 # metadata. It has better performance, especially when more data
945 # is used. It also supports full snapshots.
947 sparse_segtype_default = "thin"
949 # Configuration option global/lvdisplay_shows_full_device_path.
950 # Enable this to reinstate the previous lvdisplay name format.
951 # The default format for displaying LV names in lvdisplay was changed
952 # in version 2.02.89 to show the LV name and path separately.
953 # Previously this was always shown as /dev/vgname/lvname even when that
954 # was never a valid path in the /dev filesystem.
955 # This configuration option has an automatic default value.
956 # lvdisplay_shows_full_device_path = 0
958 # Configuration option global/event_activation.
959 # Activate LVs based on system-generated device events.
960 # When a device appears on the system, a system-generated event runs
961 # the pvscan command to activate LVs if the new PV completes the VG.
962 # Use auto_activation_volume_list to select which LVs should be
963 # activated from these events (the default is all.)
964 # When event_activation is disabled, the system will generally run
965 # a direct activation command to activate LVs in complete VGs.
968 # Configuration option global/use_aio.
969 # Use async I/O when reading and writing devices.
970 # This configuration option has an automatic default value.
973 # Configuration option global/use_lvmlockd.
974 # Use lvmlockd for locking among hosts using LVM on shared storage.
975 # Applicable only if LVM is compiled with lockd support in which
976 # case there is also lvmlockd(8) man page available for more
980 # Configuration option global/lvmlockd_lock_retries.
981 # Retry lvmlockd lock requests this many times.
982 # Applicable only if LVM is compiled with lockd support
983 # This configuration option has an automatic default value.
984 # lvmlockd_lock_retries = 3
986 # Configuration option global/sanlock_lv_extend.
987 # Size in MiB to extend the internal LV holding sanlock locks.
988 # The internal LV holds locks for each LV in the VG, and after enough
989 # LVs have been created, the internal LV needs to be extended. lvcreate
990 # will automatically extend the internal LV when needed by the amount
991 # specified here. Setting this to 0 disables the automatic extension
992 # and can cause lvcreate to fail. Applicable only if LVM is compiled
994 # This configuration option has an automatic default value.
995 # sanlock_lv_extend = 256
997 # Configuration option global/thin_check_executable.
998 # The full path to the thin_check command.
999 # LVM uses this command to check that a thin metadata device is in a
1000 # usable state. When a thin pool is activated and after it is
1001 # deactivated, this command is run. Activation will only proceed if
1002 # the command has an exit status of 0. Set to "" to skip this check.
1003 # (Not recommended.) Also see thin_check_options.
1004 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1005 # This configuration option has an automatic default value.
1006 # thin_check_executable = "/usr/sbin/thin_check"
1008 # Configuration option global/thin_dump_executable.
1009 # The full path to the thin_dump command.
1010 # LVM uses this command to dump thin pool metadata.
1011 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1012 # This configuration option has an automatic default value.
1013 # thin_dump_executable = "/usr/sbin/thin_dump"
1015 # Configuration option global/thin_repair_executable.
1016 # The full path to the thin_repair command.
1017 # LVM uses this command to repair a thin metadata device if it is in
1018 # an unusable state. Also see thin_repair_options.
1019 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1020 # This configuration option has an automatic default value.
1021 # thin_repair_executable = "/usr/sbin/thin_repair"
1023 # Configuration option global/thin_check_options.
1024 # List of options passed to the thin_check command.
1025 # With thin_check version 2.1 or newer you can add the option
1026 # --ignore-non-fatal-errors to let it pass through ignorable errors
1027 # and fix them later. With thin_check version 3.2 or newer you should
1028 # include the option --clear-needs-check-flag.
1029 # This configuration option has an automatic default value.
1030 # thin_check_options = [ "-q", "--clear-needs-check-flag" ]
1032 # Configuration option global/thin_repair_options.
1033 # List of options passed to the thin_repair command.
1034 # This configuration option has an automatic default value.
1035 # thin_repair_options = [ "" ]
1037 # Configuration option global/thin_disabled_features.
1038 # Features to not use in the thin driver.
1039 # This can be helpful for testing, or to avoid using a feature that is
1040 # causing problems. Features include: block_size, discards,
1041 # discards_non_power_2, external_origin, metadata_resize,
1042 # external_origin_extend, error_if_no_space.
1045 # thin_disabled_features = [ "discards", "block_size" ]
1047 # This configuration option does not have a default value defined.
1049 # Configuration option global/cache_disabled_features.
1050 # Features to not use in the cache driver.
1051 # This can be helpful for testing, or to avoid using a feature that is
1052 # causing problems. Features include: policy_mq, policy_smq, metadata2.
1055 # cache_disabled_features = [ "policy_smq" ]
1057 # This configuration option does not have a default value defined.
1059 # Configuration option global/cache_check_executable.
1060 # The full path to the cache_check command.
1061 # LVM uses this command to check that a cache metadata device is in a
1062 # usable state. When a cached LV is activated and after it is
1063 # deactivated, this command is run. Activation will only proceed if the
1064 # command has an exit status of 0. Set to "" to skip this check.
1065 # (Not recommended.) Also see cache_check_options.
1066 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1067 # This configuration option has an automatic default value.
1068 # cache_check_executable = "/usr/sbin/cache_check"
1070 # Configuration option global/cache_dump_executable.
1071 # The full path to the cache_dump command.
1072 # LVM uses this command to dump cache pool metadata.
1073 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1074 # This configuration option has an automatic default value.
1075 # cache_dump_executable = "/usr/sbin/cache_dump"
1077 # Configuration option global/cache_repair_executable.
1078 # The full path to the cache_repair command.
1079 # LVM uses this command to repair a cache metadata device if it is in
1080 # an unusable state. Also see cache_repair_options.
1081 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1082 # This configuration option has an automatic default value.
1083 # cache_repair_executable = "/usr/sbin/cache_repair"
1085 # Configuration option global/cache_check_options.
1086 # List of options passed to the cache_check command.
1087 # With cache_check version 5.0 or newer you should include the option
1088 # --clear-needs-check-flag.
1089 # This configuration option has an automatic default value.
1090 # cache_check_options = [ "-q", "--clear-needs-check-flag" ]
1092 # Configuration option global/cache_repair_options.
1093 # List of options passed to the cache_repair command.
1094 # This configuration option has an automatic default value.
1095 # cache_repair_options = [ "" ]
1097 # Configuration option global/vdo_format_executable.
1098 # The full path to the vdoformat command.
1099 # LVM uses this command to initial data volume for VDO type logical volume
1100 # This configuration option has an automatic default value.
1101 # vdo_format_executable = "autodetect"
1103 # Configuration option global/vdo_format_options.
1104 # List of options passed added to standard vdoformat command.
1105 # This configuration option has an automatic default value.
1106 # vdo_format_options = [ "" ]
1108 # Configuration option global/fsadm_executable.
1109 # The full path to the fsadm command.
1110 # LVM uses this command to help with lvresize -r operations.
1111 # This configuration option has an automatic default value.
1112 # fsadm_executable = "/sbin/fsadm"
1114 # Configuration option global/system_id_source.
1115 # The method LVM uses to set the local system ID.
1116 # Volume Groups can also be given a system ID (by vgcreate, vgchange,
1117 # or vgimport.) A VG on shared storage devices is accessible only to
1118 # the host with a matching system ID. See 'man lvmsystemid' for
1119 # information on limitations and correct usage.
1123 # The host has no system ID.
1125 # Obtain the system ID from the system_id setting in the 'local'
1126 # section of an lvm configuration file, e.g. lvmlocal.conf.
1128 # Set the system ID from the hostname (uname) of the system.
1129 # System IDs beginning localhost are not permitted.
1131 # Use the contents of the machine-id file to set the system ID.
1132 # Some systems create this file at installation time.
1133 # See 'man machine-id' and global/etc.
1135 # Use the contents of another file (system_id_file) to set the
1138 system_id_source = "none"
1140 # Configuration option global/system_id_file.
1141 # The full path to the file containing a system ID.
1142 # This is used when system_id_source is set to 'file'.
1143 # Comments starting with the character # are ignored.
1144 # This configuration option does not have a default value defined.
1146 # Configuration option global/use_lvmpolld.
1147 # Use lvmpolld to supervise long running LVM commands.
1148 # When enabled, control of long running LVM commands is transferred
1149 # from the original LVM command to the lvmpolld daemon. This allows
1150 # the operation to continue independent of the original LVM command.
1151 # After lvmpolld takes over, the LVM command displays the progress
1152 # of the ongoing operation. lvmpolld itself runs LVM commands to
1153 # manage the progress of ongoing operations. lvmpolld can be used as
1154 # a native systemd service, which allows it to be started on demand,
1155 # and to use its own control group. When this option is disabled, LVM
1156 # commands will supervise long running operations by forking themselves.
1157 # Applicable only if LVM is compiled with lvmpolld support.
1160 # Configuration option global/notify_dbus.
1161 # Enable D-Bus notification from LVM commands.
1162 # When enabled, an LVM command that changes PVs, changes VG metadata,
1163 # or changes the activation state of an LV will send a notification.
1167 # Configuration section activation.
1170 # Configuration option activation/checks.
1171 # Perform internal checks of libdevmapper operations.
1172 # Useful for debugging problems with activation. Some of the checks may
1173 # be expensive, so it's best to use this only when there seems to be a
1177 # Configuration option activation/udev_sync.
1178 # Use udev notifications to synchronize udev and LVM.
1179 # The --nodevsync option overrides this setting.
1180 # When disabled, LVM commands will not wait for notifications from
1181 # udev, but continue irrespective of any possible udev processing in
1182 # the background. Only use this if udev is not running or has rules
1183 # that ignore the devices LVM creates. If enabled when udev is not
1184 # running, and LVM processes are waiting for udev, run the command
1185 # 'dmsetup udevcomplete_all' to wake them up.
1188 # Configuration option activation/udev_rules.
1189 # Use udev rules to manage LV device nodes and symlinks.
1190 # When disabled, LVM will manage the device nodes and symlinks for
1191 # active LVs itself. Manual intervention may be required if this
1192 # setting is changed while LVs are active.
1195 # Configuration option activation/verify_udev_operations.
1196 # Use extra checks in LVM to verify udev operations.
1197 # This enables additional checks (and if necessary, repairs) on entries
1198 # in the device directory after udev has completed processing its
1199 # events. Useful for diagnosing problems with LVM/udev interactions.
1200 verify_udev_operations = 0
1202 # Configuration option activation/retry_deactivation.
1203 # Retry failed LV deactivation.
1204 # If LV deactivation fails, LVM will retry for a few seconds before
1205 # failing. This may happen because a process run from a quick udev rule
1206 # temporarily opened the device.
1207 retry_deactivation = 1
1209 # Configuration option activation/missing_stripe_filler.
1210 # Method to fill missing stripes when activating an incomplete LV.
1211 # Using 'error' will make inaccessible parts of the device return I/O
1212 # errors on access. Using 'zero' will return success (and zero) on I/O
1213 # You can instead use a device path, in which case,
1214 # that device will be used in place of missing stripes. Using anything
1215 # other than 'error' with mirrored or snapshotted volumes is likely to
1216 # result in data corruption.
1217 # This configuration option is advanced.
1218 missing_stripe_filler = "error"
1220 # Configuration option activation/use_linear_target.
1221 # Use the linear target to optimize single stripe LVs.
1222 # When disabled, the striped target is used. The linear target is an
1223 # optimised version of the striped target that only handles a single
1225 use_linear_target = 1
1227 # Configuration option activation/reserved_stack.
1228 # Stack size in KiB to reserve for use while devices are suspended.
1229 # Insufficent reserve risks I/O deadlock during device suspension.
1232 # Configuration option activation/reserved_memory.
1233 # Memory size in KiB to reserve for use while devices are suspended.
1234 # Insufficent reserve risks I/O deadlock during device suspension.
1235 reserved_memory = 8192
1237 # Configuration option activation/process_priority.
1238 # Nice value used while devices are suspended.
1239 # Use a high priority so that LVs are suspended
1240 # for the shortest possible time.
1241 process_priority = -18
1243 # Configuration option activation/volume_list.
1244 # Only LVs selected by this list are activated.
1245 # If this list is defined, an LV is only activated if it matches an
1246 # entry in this list. If this list is undefined, it imposes no limits
1247 # on LV activation (all are allowed).
1251 # The VG name is matched exactly and selects all LVs in the VG.
1253 # The VG name and LV name are matched exactly and selects the LV.
1255 # Selects an LV if the specified tag matches a tag set on the LV
1258 # Selects an LV if a tag defined on the host is also set on the LV
1259 # or VG. See tags/hosttags. If any host tags exist but volume_list
1260 # is not defined, a default single-entry list containing '@*'
1264 # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1266 # This configuration option does not have a default value defined.
1268 # Configuration option activation/auto_activation_volume_list.
1269 # Only LVs selected by this list are auto-activated.
1270 # This list works like volume_list, but it is used only by
1271 # auto-activation commands. It does not apply to direct activation
1272 # commands. If this list is defined, an LV is only auto-activated
1273 # if it matches an entry in this list. If this list is undefined, it
1274 # imposes no limits on LV auto-activation (all are allowed.) If this
1275 # list is defined and empty, i.e. "[]", then no LVs are selected for
1276 # auto-activation. An LV that is selected by this list for
1277 # auto-activation, must also be selected by volume_list (if defined)
1278 # before it is activated. Auto-activation is an activation command that
1279 # includes the 'a' argument: --activate ay or -a ay. The 'a' (auto)
1280 # argument for auto-activation is meant to be used by activation
1281 # commands that are run automatically by the system, as opposed to LVM
1282 # commands run directly by a user. A user may also use the 'a' flag
1283 # directly to perform auto-activation. Also see pvscan(8) for more
1284 # information about auto-activation.
1288 # The VG name is matched exactly and selects all LVs in the VG.
1290 # The VG name and LV name are matched exactly and selects the LV.
1292 # Selects an LV if the specified tag matches a tag set on the LV
1295 # Selects an LV if a tag defined on the host is also set on the LV
1296 # or VG. See tags/hosttags. If any host tags exist but volume_list
1297 # is not defined, a default single-entry list containing '@*'
1301 # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1303 # This configuration option does not have a default value defined.
1305 # Configuration option activation/read_only_volume_list.
1306 # LVs in this list are activated in read-only mode.
1307 # If this list is defined, each LV that is to be activated is checked
1308 # against this list, and if it matches, it is activated in read-only
1309 # mode. This overrides the permission setting stored in the metadata,
1310 # e.g. from --permission rw.
1314 # The VG name is matched exactly and selects all LVs in the VG.
1316 # The VG name and LV name are matched exactly and selects the LV.
1318 # Selects an LV if the specified tag matches a tag set on the LV
1321 # Selects an LV if a tag defined on the host is also set on the LV
1322 # or VG. See tags/hosttags. If any host tags exist but volume_list
1323 # is not defined, a default single-entry list containing '@*'
1327 # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1329 # This configuration option does not have a default value defined.
1331 # Configuration option activation/raid_region_size.
1332 # Size in KiB of each raid or mirror synchronization region.
1333 # The clean/dirty state of data is tracked for each region.
1334 # The value is rounded down to a power of two if necessary, and
1335 # is ignored if it is not a multiple of the machine memory page size.
1336 raid_region_size = 2048
1338 # Configuration option activation/error_when_full.
1339 # Return errors if a thin pool runs out of space.
1340 # The --errorwhenfull option overrides this setting.
1341 # When enabled, writes to thin LVs immediately return an error if the
1342 # thin pool is out of data space. When disabled, writes to thin LVs
1343 # are queued if the thin pool is out of space, and processed when the
1344 # thin pool data space is extended. New thin pools are assigned the
1345 # behavior defined here.
1346 # This configuration option has an automatic default value.
1347 # error_when_full = 0
1349 # Configuration option activation/readahead.
1350 # Setting to use when there is no readahead setting in metadata.
1354 # Disable readahead.
1356 # Use default value chosen by kernel.
1360 # Configuration option activation/raid_fault_policy.
1361 # Defines how a device failure in a RAID LV is handled.
1362 # This includes LVs that have the following segment types:
1363 # raid1, raid4, raid5*, and raid6*.
1364 # If a device in the LV fails, the policy determines the steps
1365 # performed by dmeventd automatically, and the steps perfomed by the
1366 # manual command lvconvert --repair --use-policies.
1367 # Automatic handling requires dmeventd to be monitoring the LV.
1371 # Use the system log to warn the user that a device in the RAID LV
1372 # has failed. It is left to the user to run lvconvert --repair
1373 # manually to remove or replace the failed device. As long as the
1374 # number of failed devices does not exceed the redundancy of the LV
1375 # (1 device for raid4/5, 2 for raid6), the LV will remain usable.
1377 # Attempt to use any extra physical volumes in the VG as spares and
1378 # replace faulty devices.
1380 raid_fault_policy = "warn"
1382 # Configuration option activation/mirror_image_fault_policy.
1383 # Defines how a device failure in a 'mirror' LV is handled.
1384 # An LV with the 'mirror' segment type is composed of mirror images
1385 # (copies) and a mirror log. A disk log ensures that a mirror LV does
1386 # not need to be re-synced (all copies made the same) every time a
1387 # machine reboots or crashes. If a device in the LV fails, this policy
1388 # determines the steps perfomed by dmeventd automatically, and the steps
1389 # performed by the manual command lvconvert --repair --use-policies.
1390 # Automatic handling requires dmeventd to be monitoring the LV.
1394 # Simply remove the faulty device and run without it. If the log
1395 # device fails, the mirror would convert to using an in-memory log.
1396 # This means the mirror will not remember its sync status across
1397 # crashes/reboots and the entire mirror will be re-synced. If a
1398 # mirror image fails, the mirror will convert to a non-mirrored
1399 # device if there is only one remaining good copy.
1401 # Remove the faulty device and try to allocate space on a new
1402 # device to be a replacement for the failed device. Using this
1403 # policy for the log is fast and maintains the ability to remember
1404 # sync state through crashes/reboots. Using this policy for a
1405 # mirror device is slow, as it requires the mirror to resynchronize
1406 # the devices, but it will preserve the mirror characteristic of
1407 # the device. This policy acts like 'remove' if no suitable device
1408 # and space can be allocated for the replacement.
1410 # Not yet implemented. Useful to place the log device temporarily
1411 # on the same physical volume as one of the mirror images. This
1412 # policy is not recommended for mirror devices since it would break
1413 # the redundant nature of the mirror. This policy acts like
1414 # 'remove' if no suitable device and space can be allocated for the
1417 mirror_image_fault_policy = "remove"
1419 # Configuration option activation/mirror_log_fault_policy.
1420 # Defines how a device failure in a 'mirror' log LV is handled.
1421 # The mirror_image_fault_policy description for mirrored LVs also
1422 # applies to mirrored log LVs.
1423 mirror_log_fault_policy = "allocate"
1425 # Configuration option activation/snapshot_autoextend_threshold.
1426 # Auto-extend a snapshot when its usage exceeds this percent.
1427 # Setting this to 100 disables automatic extension.
1428 # The minimum value is 50 (a smaller value is treated as 50.)
1429 # Also see snapshot_autoextend_percent.
1430 # Automatic extension requires dmeventd to be monitoring the LV.
1433 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1434 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1435 # 840M, it is extended to 1.44G:
1436 # snapshot_autoextend_threshold = 70
1438 snapshot_autoextend_threshold = 100
1440 # Configuration option activation/snapshot_autoextend_percent.
1441 # Auto-extending a snapshot adds this percent extra space.
1442 # The amount of additional space added to a snapshot is this
1443 # percent of its current size.
1446 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1447 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1448 # 840M, it is extended to 1.44G:
1449 # snapshot_autoextend_percent = 20
1451 snapshot_autoextend_percent = 20
1453 # Configuration option activation/thin_pool_autoextend_threshold.
1454 # Auto-extend a thin pool when its usage exceeds this percent.
1455 # Setting this to 100 disables automatic extension.
1456 # The minimum value is 50 (a smaller value is treated as 50.)
1457 # Also see thin_pool_autoextend_percent.
1458 # Automatic extension requires dmeventd to be monitoring the LV.
1461 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1462 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1463 # 840M, it is extended to 1.44G:
1464 # thin_pool_autoextend_threshold = 70
1466 thin_pool_autoextend_threshold = 100
1468 # Configuration option activation/thin_pool_autoextend_percent.
1469 # Auto-extending a thin pool adds this percent extra space.
1470 # The amount of additional space added to a thin pool is this
1471 # percent of its current size.
1474 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1475 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1476 # 840M, it is extended to 1.44G:
1477 # thin_pool_autoextend_percent = 20
1479 thin_pool_autoextend_percent = 20
1481 # Configuration option activation/vdo_pool_autoextend_threshold.
1482 # Auto-extend a VDO pool when its usage exceeds this percent.
1483 # Setting this to 100 disables automatic extension.
1484 # The minimum value is 50 (a smaller value is treated as 50.)
1485 # Also see vdo_pool_autoextend_percent.
1486 # Automatic extension requires dmeventd to be monitoring the LV.
1489 # Using 70% autoextend threshold and 20% autoextend size, when a 10G
1490 # VDO pool exceeds 7G, it is extended to 12G, and when it exceeds
1491 # 8.4G, it is extended to 14.4G:
1492 # vdo_pool_autoextend_threshold = 70
1494 vdo_pool_autoextend_threshold = 100
1496 # Configuration option activation/vdo_pool_autoextend_percent.
1497 # Auto-extending a VDO pool adds this percent extra space.
1498 # The amount of additional space added to a VDO pool is this
1499 # percent of its current size.
1502 # Using 70% autoextend threshold and 20% autoextend size, when a 10G
1503 # VDO pool exceeds 7G, it is extended to 12G, and when it exceeds
1504 # 8.4G, it is extended to 14.4G:
1505 # This configuration option has an automatic default value.
1506 # vdo_pool_autoextend_percent = 20
1508 # Configuration option activation/mlock_filter.
1509 # Do not mlock these memory areas.
1510 # While activating devices, I/O to devices being (re)configured is
1511 # suspended. As a precaution against deadlocks, LVM pins memory it is
1512 # using so it is not paged out, and will not require I/O to reread.
1513 # Groups of pages that are known not to be accessed during activation
1514 # do not need to be pinned into memory. Each string listed in this
1515 # setting is compared against each line in /proc/self/maps, and the
1516 # pages corresponding to lines that match are not pinned. On some
1517 # systems, locale-archive was found to make up over 80% of the memory
1518 # used by the process.
1521 # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
1523 # This configuration option is advanced.
1524 # This configuration option does not have a default value defined.
1526 # Configuration option activation/use_mlockall.
1527 # Use the old behavior of mlockall to pin all memory.
1528 # Prior to version 2.02.62, LVM used mlockall() to pin the whole
1529 # process's memory while activating devices.
1532 # Configuration option activation/monitoring.
1533 # Monitor LVs that are activated.
1534 # The --ignoremonitoring option overrides this setting.
1535 # When enabled, LVM will ask dmeventd to monitor activated LVs.
1538 # Configuration option activation/polling_interval.
1539 # Check pvmove or lvconvert progress at this interval (seconds).
1540 # When pvmove or lvconvert must wait for the kernel to finish
1541 # synchronising or merging data, they check and report progress at
1542 # intervals of this number of seconds. If this is set to 0 and there
1543 # is only one thing to wait for, there are no progress reports, but
1544 # the process is awoken immediately once the operation is complete.
1545 polling_interval = 15
1547 # Configuration option activation/auto_set_activation_skip.
1548 # Set the activation skip flag on new thin snapshot LVs.
1549 # The --setactivationskip option overrides this setting.
1550 # An LV can have a persistent 'activation skip' flag. The flag causes
1551 # the LV to be skipped during normal activation. The lvchange/vgchange
1552 # -K option is required to activate LVs that have the activation skip
1553 # flag set. When this setting is enabled, the activation skip flag is
1554 # set on new thin snapshot LVs.
1555 # This configuration option has an automatic default value.
1556 # auto_set_activation_skip = 1
1558 # Configuration option activation/activation_mode.
1559 # How LVs with missing devices are activated.
1560 # The --activationmode option overrides this setting.
1564 # Only allow activation of an LV if all of the Physical Volumes it
1565 # uses are present. Other PVs in the Volume Group may be missing.
1567 # Like complete, but additionally RAID LVs of segment type raid1,
1568 # raid4, raid5, radid6 and raid10 will be activated if there is no
1569 # data loss, i.e. they have sufficient redundancy to present the
1570 # entire addressable range of the Logical Volume.
1572 # Allows the activation of any LV even if a missing or failed PV
1573 # could cause data loss with a portion of the LV inaccessible.
1574 # This setting should not normally be used, but may sometimes
1575 # assist with data recovery.
1577 activation_mode = "degraded"
1579 # Configuration option activation/lock_start_list.
1580 # Locking is started only for VGs selected by this list.
1581 # The rules are the same as those for volume_list.
1582 # This configuration option does not have a default value defined.
1584 # Configuration option activation/auto_lock_start_list.
1585 # Locking is auto-started only for VGs selected by this list.
1586 # The rules are the same as those for auto_activation_volume_list.
1587 # This configuration option does not have a default value defined.
1590 # Configuration section metadata.
1591 # This configuration section has an automatic default value.
1594 # Configuration option metadata/check_pv_device_sizes.
1595 # Check device sizes are not smaller than corresponding PV sizes.
1596 # If device size is less than corresponding PV size found in metadata,
1597 # there is always a risk of data loss. If this option is set, then LVM
1598 # issues a warning message each time it finds that the device size is
1599 # less than corresponding PV size. You should not disable this unless
1600 # you are absolutely sure about what you are doing!
1601 # This configuration option is advanced.
1602 # This configuration option has an automatic default value.
1603 # check_pv_device_sizes = 1
1605 # Configuration option metadata/record_lvs_history.
1606 # When enabled, LVM keeps history records about removed LVs in
1607 # metadata. The information that is recorded in metadata for
1608 # historical LVs is reduced when compared to original
1609 # information kept in metadata for live LVs. Currently, this
1610 # feature is supported for thin and thin snapshot LVs only.
1611 # This configuration option has an automatic default value.
1612 # record_lvs_history = 0
1614 # Configuration option metadata/lvs_history_retention_time.
1615 # Retention time in seconds after which a record about individual
1616 # historical logical volume is automatically destroyed.
1617 # A value of 0 disables this feature.
1618 # This configuration option has an automatic default value.
1619 # lvs_history_retention_time = 0
1621 # Configuration option metadata/pvmetadatacopies.
1622 # Number of copies of metadata to store on each PV.
1623 # The --pvmetadatacopies option overrides this setting.
1627 # Two copies of the VG metadata are stored on the PV, one at the
1628 # front of the PV, and one at the end.
1630 # One copy of VG metadata is stored at the front of the PV.
1632 # No copies of VG metadata are stored on the PV. This may be
1633 # useful for VGs containing large numbers of PVs.
1635 # This configuration option is advanced.
1636 # This configuration option has an automatic default value.
1637 # pvmetadatacopies = 1
1639 # Configuration option metadata/vgmetadatacopies.
1640 # Number of copies of metadata to maintain for each VG.
1641 # The --vgmetadatacopies option overrides this setting.
1642 # If set to a non-zero value, LVM automatically chooses which of the
1643 # available metadata areas to use to achieve the requested number of
1644 # copies of the VG metadata. If you set a value larger than the the
1645 # total number of metadata areas available, then metadata is stored in
1646 # them all. The value 0 (unmanaged) disables this automatic management
1647 # and allows you to control which metadata areas are used at the
1648 # individual PV level using pvchange --metadataignore y|n.
1649 # This configuration option has an automatic default value.
1650 # vgmetadatacopies = 0
1652 # Configuration option metadata/pvmetadatasize.
1653 # The default size of the metadata area in units of 512 byte sectors.
1654 # The metadata area begins at an offset of the page size from the start
1655 # of the device. The first PE is by default at 1 MiB from the start of
1656 # the device. The space between these is the default metadata area size.
1657 # The actual size of the metadata area may be larger than what is set
1658 # here due to default_data_alignment making the first PE a MiB multiple.
1659 # The metadata area begins with a 512 byte header and is followed by a
1660 # circular buffer used for VG metadata text. The maximum size of the VG
1661 # metadata is about half the size of the metadata buffer. VGs with large
1662 # numbers of PVs or LVs, or VGs containing complex LV structures, may need
1663 # additional space for VG metadata. The --metadatasize option overrides
1665 # This configuration option does not have a default value defined.
1666 # This configuration option has an automatic default value.
1668 # Configuration option metadata/pvmetadataignore.
1669 # Ignore metadata areas on a new PV.
1670 # The --metadataignore option overrides this setting.
1671 # If metadata areas on a PV are ignored, LVM will not store metadata
1673 # This configuration option is advanced.
1674 # This configuration option has an automatic default value.
1675 # pvmetadataignore = 0
1677 # Configuration option metadata/stripesize.
1678 # This configuration option is advanced.
1679 # This configuration option has an automatic default value.
1683 # Configuration section report.
1684 # LVM report command output formatting.
1685 # This configuration section has an automatic default value.
1688 # Configuration option report/output_format.
1689 # Format of LVM command's report output.
1690 # If there is more than one report per command, then the format
1691 # is applied for all reports. You can also change output format
1692 # directly on command line using --reportformat option which
1693 # has precedence over log/output_format setting.
1696 # Original format with columns and rows. If there is more than
1697 # one report per command, each report is prefixed with report's
1698 # name for identification.
1701 # This configuration option has an automatic default value.
1702 # output_format = "basic"
1704 # Configuration option report/compact_output.
1705 # Do not print empty values for all report fields.
1706 # If enabled, all fields that don't have a value set for any of the
1707 # rows reported are skipped and not printed. Compact output is
1708 # applicable only if report/buffered is enabled. If you need to
1709 # compact only specified fields, use compact_output=0 and define
1710 # report/compact_output_cols configuration setting instead.
1711 # This configuration option has an automatic default value.
1712 # compact_output = 0
1714 # Configuration option report/compact_output_cols.
1715 # Do not print empty values for specified report fields.
1716 # If defined, specified fields that don't have a value set for any
1717 # of the rows reported are skipped and not printed. Compact output
1718 # is applicable only if report/buffered is enabled. If you need to
1719 # compact all fields, use compact_output=1 instead in which case
1720 # the compact_output_cols setting is then ignored.
1721 # This configuration option has an automatic default value.
1722 # compact_output_cols = ""
1724 # Configuration option report/aligned.
1725 # Align columns in report output.
1726 # This configuration option has an automatic default value.
1729 # Configuration option report/buffered.
1730 # Buffer report output.
1731 # When buffered reporting is used, the report's content is appended
1732 # incrementally to include each object being reported until the report
1733 # is flushed to output which normally happens at the end of command
1734 # execution. Otherwise, if buffering is not used, each object is
1735 # reported as soon as its processing is finished.
1736 # This configuration option has an automatic default value.
1739 # Configuration option report/headings.
1740 # Show headings for columns on report.
1741 # This configuration option has an automatic default value.
1744 # Configuration option report/separator.
1745 # A separator to use on report after each field.
1746 # This configuration option has an automatic default value.
1749 # Configuration option report/list_item_separator.
1750 # A separator to use for list items when reported.
1751 # This configuration option has an automatic default value.
1752 # list_item_separator = ","
1754 # Configuration option report/prefixes.
1755 # Use a field name prefix for each field reported.
1756 # This configuration option has an automatic default value.
1759 # Configuration option report/quoted.
1760 # Quote field values when using field name prefixes.
1761 # This configuration option has an automatic default value.
1764 # Configuration option report/columns_as_rows.
1765 # Output each column as a row.
1766 # If set, this also implies report/prefixes=1.
1767 # This configuration option has an automatic default value.
1768 # columns_as_rows = 0
1770 # Configuration option report/binary_values_as_numeric.
1771 # Use binary values 0 or 1 instead of descriptive literal values.
1772 # For columns that have exactly two valid values to report
1773 # (not counting the 'unknown' value which denotes that the
1774 # value could not be determined).
1775 # This configuration option has an automatic default value.
1776 # binary_values_as_numeric = 0
1778 # Configuration option report/time_format.
1779 # Set time format for fields reporting time values.
1780 # Format specification is a string which may contain special character
1781 # sequences and ordinary character sequences. Ordinary character
1782 # sequences are copied verbatim. Each special character sequence is
1783 # introduced by the '%' character and such sequence is then
1784 # substituted with a value as described below.
1788 # The abbreviated name of the day of the week according to the
1791 # The full name of the day of the week according to the current
1794 # The abbreviated month name according to the current locale.
1796 # The full month name according to the current locale.
1798 # The preferred date and time representation for the current
1801 # The century number (year/100) as a 2-digit integer. (alt E)
1803 # The day of the month as a decimal number (range 01 to 31).
1806 # Equivalent to %m/%d/%y. (For Americans only. Americans should
1807 # note that in other countries%d/%m/%y is rather common. This
1808 # means that in international context this format is ambiguous and
1809 # should not be used.
1811 # Like %d, the day of the month as a decimal number, but a leading
1812 # zero is replaced by a space. (alt O)
1814 # Modifier: use alternative local-dependent representation if
1817 # Equivalent to %Y-%m-%d (the ISO 8601 date format).
1819 # The ISO 8601 week-based year with century as adecimal number.
1820 # The 4-digit year corresponding to the ISO week number (see %V).
1821 # This has the same format and value as %Y, except that if the
1822 # ISO week number belongs to the previous or next year, that year
1825 # Like %G, but without century, that is, with a 2-digit year
1830 # The hour as a decimal number using a 24-hour clock
1831 # (range 00 to 23). (alt O)
1833 # The hour as a decimal number using a 12-hour clock
1834 # (range 01 to 12). (alt O)
1836 # The day of the year as a decimal number (range 001 to 366).
1838 # The hour (24-hour clock) as a decimal number (range 0 to 23);
1839 # single digits are preceded by a blank. (See also %H.)
1841 # The hour (12-hour clock) as a decimal number (range 1 to 12);
1842 # single digits are preceded by a blank. (See also %I.)
1844 # The month as a decimal number (range 01 to 12). (alt O)
1846 # The minute as a decimal number (range 00 to 59). (alt O)
1848 # Modifier: use alternative numeric symbols.
1850 # Either "AM" or "PM" according to the given time value,
1851 # or the corresponding strings for the current locale. Noon is
1852 # treated as "PM" and midnight as "AM".
1854 # Like %p but in lowercase: "am" or "pm" or a corresponding
1855 # string for the current locale.
1857 # The time in a.m. or p.m. notation. In the POSIX locale this is
1858 # equivalent to %I:%M:%S %p.
1860 # The time in 24-hour notation (%H:%M). For a version including
1861 # the seconds, see %T below.
1863 # The number of seconds since the Epoch,
1864 # 1970-01-01 00:00:00 +0000 (UTC)
1866 # The second as a decimal number (range 00 to 60). (The range is
1867 # up to 60 to allow for occasional leap seconds.) (alt O)
1871 # The time in 24-hour notation (%H:%M:%S).
1873 # The day of the week as a decimal, range 1 to 7, Monday being 1.
1874 # See also %w. (alt O)
1876 # The week number of the current year as a decimal number,
1877 # range 00 to 53, starting with the first Sunday as the first
1878 # day of week 01. See also %V and %W. (alt O)
1880 # The ISO 8601 week number of the current year as a decimal number,
1881 # range 01 to 53, where week 1 is the first week that has at least
1882 # 4 days in the new year. See also %U and %W. (alt O)
1884 # The day of the week as a decimal, range 0 to 6, Sunday being 0.
1885 # See also %u. (alt O)
1887 # The week number of the current year as a decimal number,
1888 # range 00 to 53, starting with the first Monday as the first day
1889 # of week 01. (alt O)
1891 # The preferred date representation for the current locale without
1894 # The preferred time representation for the current locale without
1897 # The year as a decimal number without a century (range 00 to 99).
1900 # The year as a decimal number including the century. (alt E)
1902 # The +hhmm or -hhmm numeric timezone (that is, the hour and minute
1905 # The timezone name or abbreviation.
1907 # A literal '%' character.
1909 # This configuration option has an automatic default value.
1910 # time_format = "%Y-%m-%d %T %z"
1912 # Configuration option report/devtypes_sort.
1913 # List of columns to sort by when reporting 'lvm devtypes' command.
1914 # See 'lvm devtypes -o help' for the list of possible fields.
1915 # This configuration option has an automatic default value.
1916 # devtypes_sort = "devtype_name"
1918 # Configuration option report/devtypes_cols.
1919 # List of columns to report for 'lvm devtypes' command.
1920 # See 'lvm devtypes -o help' for the list of possible fields.
1921 # This configuration option has an automatic default value.
1922 # devtypes_cols = "devtype_name,devtype_max_partitions,devtype_description"
1924 # Configuration option report/devtypes_cols_verbose.
1925 # List of columns to report for 'lvm devtypes' command in verbose mode.
1926 # See 'lvm devtypes -o help' for the list of possible fields.
1927 # This configuration option has an automatic default value.
1928 # devtypes_cols_verbose = "devtype_name,devtype_max_partitions,devtype_description"
1930 # Configuration option report/lvs_sort.
1931 # List of columns to sort by when reporting 'lvs' command.
1932 # See 'lvs -o help' for the list of possible fields.
1933 # This configuration option has an automatic default value.
1934 # lvs_sort = "vg_name,lv_name"
1936 # Configuration option report/lvs_cols.
1937 # List of columns to report for 'lvs' command.
1938 # See 'lvs -o help' for the list of possible fields.
1939 # This configuration option has an automatic default value.
1940 # lvs_cols = "lv_name,vg_name,lv_attr,lv_size,pool_lv,origin,data_percent,metadata_percent,move_pv,mirror_log,copy_percent,convert_lv"
1942 # Configuration option report/lvs_cols_verbose.
1943 # List of columns to report for 'lvs' command in verbose mode.
1944 # See 'lvs -o help' for the list of possible fields.
1945 # This configuration option has an automatic default value.
1946 # lvs_cols_verbose = "lv_name,vg_name,seg_count,lv_attr,lv_size,lv_major,lv_minor,lv_kernel_major,lv_kernel_minor,pool_lv,origin,data_percent,metadata_percent,move_pv,copy_percent,mirror_log,convert_lv,lv_uuid,lv_profile"
1948 # Configuration option report/vgs_sort.
1949 # List of columns to sort by when reporting 'vgs' command.
1950 # See 'vgs -o help' for the list of possible fields.
1951 # This configuration option has an automatic default value.
1952 # vgs_sort = "vg_name"
1954 # Configuration option report/vgs_cols.
1955 # List of columns to report for 'vgs' command.
1956 # See 'vgs -o help' for the list of possible fields.
1957 # This configuration option has an automatic default value.
1958 # vgs_cols = "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
1960 # Configuration option report/vgs_cols_verbose.
1961 # List of columns to report for 'vgs' command in verbose mode.
1962 # See 'vgs -o help' for the list of possible fields.
1963 # This configuration option has an automatic default value.
1964 # vgs_cols_verbose = "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
1966 # Configuration option report/pvs_sort.
1967 # List of columns to sort by when reporting 'pvs' command.
1968 # See 'pvs -o help' for the list of possible fields.
1969 # This configuration option has an automatic default value.
1970 # pvs_sort = "pv_name"
1972 # Configuration option report/pvs_cols.
1973 # List of columns to report for 'pvs' command.
1974 # See 'pvs -o help' for the list of possible fields.
1975 # This configuration option has an automatic default value.
1976 # pvs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
1978 # Configuration option report/pvs_cols_verbose.
1979 # List of columns to report for 'pvs' command in verbose mode.
1980 # See 'pvs -o help' for the list of possible fields.
1981 # This configuration option has an automatic default value.
1982 # pvs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
1984 # Configuration option report/segs_sort.
1985 # List of columns to sort by when reporting 'lvs --segments' command.
1986 # See 'lvs --segments -o help' for the list of possible fields.
1987 # This configuration option has an automatic default value.
1988 # segs_sort = "vg_name,lv_name,seg_start"
1990 # Configuration option report/segs_cols.
1991 # List of columns to report for 'lvs --segments' command.
1992 # See 'lvs --segments -o help' for the list of possible fields.
1993 # This configuration option has an automatic default value.
1994 # segs_cols = "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
1996 # Configuration option report/segs_cols_verbose.
1997 # List of columns to report for 'lvs --segments' command in verbose mode.
1998 # See 'lvs --segments -o help' for the list of possible fields.
1999 # This configuration option has an automatic default value.
2000 # segs_cols_verbose = "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
2002 # Configuration option report/pvsegs_sort.
2003 # List of columns to sort by when reporting 'pvs --segments' command.
2004 # See 'pvs --segments -o help' for the list of possible fields.
2005 # This configuration option has an automatic default value.
2006 # pvsegs_sort = "pv_name,pvseg_start"
2008 # Configuration option report/pvsegs_cols.
2009 # List of columns to sort by when reporting 'pvs --segments' command.
2010 # See 'pvs --segments -o help' for the list of possible fields.
2011 # This configuration option has an automatic default value.
2012 # pvsegs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
2014 # Configuration option report/pvsegs_cols_verbose.
2015 # List of columns to sort by when reporting 'pvs --segments' command in verbose mode.
2016 # See 'pvs --segments -o help' for the list of possible fields.
2017 # This configuration option has an automatic default value.
2018 # pvsegs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size,lv_name,seg_start_pe,segtype,seg_pe_ranges"
2020 # Configuration option report/vgs_cols_full.
2021 # List of columns to report for lvm fullreport's 'vgs' subreport.
2022 # See 'vgs -o help' for the list of possible fields.
2023 # This configuration option has an automatic default value.
2024 # vgs_cols_full = "vg_all"
2026 # Configuration option report/pvs_cols_full.
2027 # List of columns to report for lvm fullreport's 'vgs' subreport.
2028 # See 'pvs -o help' for the list of possible fields.
2029 # This configuration option has an automatic default value.
2030 # pvs_cols_full = "pv_all"
2032 # Configuration option report/lvs_cols_full.
2033 # List of columns to report for lvm fullreport's 'lvs' subreport.
2034 # See 'lvs -o help' for the list of possible fields.
2035 # This configuration option has an automatic default value.
2036 # lvs_cols_full = "lv_all"
2038 # Configuration option report/pvsegs_cols_full.
2039 # List of columns to report for lvm fullreport's 'pvseg' subreport.
2040 # See 'pvs --segments -o help' for the list of possible fields.
2041 # This configuration option has an automatic default value.
2042 # pvsegs_cols_full = "pvseg_all,pv_uuid,lv_uuid"
2044 # Configuration option report/segs_cols_full.
2045 # List of columns to report for lvm fullreport's 'seg' subreport.
2046 # See 'lvs --segments -o help' for the list of possible fields.
2047 # This configuration option has an automatic default value.
2048 # segs_cols_full = "seg_all,lv_uuid"
2050 # Configuration option report/vgs_sort_full.
2051 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
2052 # See 'vgs -o help' for the list of possible fields.
2053 # This configuration option has an automatic default value.
2054 # vgs_sort_full = "vg_name"
2056 # Configuration option report/pvs_sort_full.
2057 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
2058 # See 'pvs -o help' for the list of possible fields.
2059 # This configuration option has an automatic default value.
2060 # pvs_sort_full = "pv_name"
2062 # Configuration option report/lvs_sort_full.
2063 # List of columns to sort by when reporting lvm fullreport's 'lvs' subreport.
2064 # See 'lvs -o help' for the list of possible fields.
2065 # This configuration option has an automatic default value.
2066 # lvs_sort_full = "vg_name,lv_name"
2068 # Configuration option report/pvsegs_sort_full.
2069 # List of columns to sort by when reporting for lvm fullreport's 'pvseg' subreport.
2070 # See 'pvs --segments -o help' for the list of possible fields.
2071 # This configuration option has an automatic default value.
2072 # pvsegs_sort_full = "pv_uuid,pvseg_start"
2074 # Configuration option report/segs_sort_full.
2075 # List of columns to sort by when reporting lvm fullreport's 'seg' subreport.
2076 # See 'lvs --segments -o help' for the list of possible fields.
2077 # This configuration option has an automatic default value.
2078 # segs_sort_full = "lv_uuid,seg_start"
2080 # Configuration option report/mark_hidden_devices.
2081 # Use brackets [] to mark hidden devices.
2082 # This configuration option has an automatic default value.
2083 # mark_hidden_devices = 1
2085 # Configuration option report/two_word_unknown_device.
2086 # Use the two words 'unknown device' in place of '[unknown]'.
2087 # This is displayed when the device for a PV is not known.
2088 # This configuration option has an automatic default value.
2089 # two_word_unknown_device = 0
2092 # Configuration section dmeventd.
2093 # Settings for the LVM event daemon.
2096 # Configuration option dmeventd/mirror_library.
2097 # The library dmeventd uses when monitoring a mirror device.
2098 # libdevmapper-event-lvm2mirror.so attempts to recover from
2099 # failures. It removes failed devices from a volume group and
2100 # reconfigures a mirror as necessary. If no mirror library is
2101 # provided, mirrors are not monitored through dmeventd.
2102 mirror_library = "libdevmapper-event-lvm2mirror.so"
2104 # Configuration option dmeventd/raid_library.
2105 # This configuration option has an automatic default value.
2106 # raid_library = "libdevmapper-event-lvm2raid.so"
2108 # Configuration option dmeventd/snapshot_library.
2109 # The library dmeventd uses when monitoring a snapshot device.
2110 # libdevmapper-event-lvm2snapshot.so monitors the filling of snapshots
2111 # and emits a warning through syslog when the usage exceeds 80%. The
2112 # warning is repeated when 85%, 90% and 95% of the snapshot is filled.
2113 snapshot_library = "libdevmapper-event-lvm2snapshot.so"
2115 # Configuration option dmeventd/thin_library.
2116 # The library dmeventd uses when monitoring a thin device.
2117 # libdevmapper-event-lvm2thin.so monitors the filling of a pool
2118 # and emits a warning through syslog when the usage exceeds 80%. The
2119 # warning is repeated when 85%, 90% and 95% of the pool is filled.
2120 thin_library = "libdevmapper-event-lvm2thin.so"
2122 # Configuration option dmeventd/thin_command.
2123 # The plugin runs command with each 5% increment when thin-pool data volume
2124 # or metadata volume gets above 50%.
2125 # Command which starts with 'lvm ' prefix is internal lvm command.
2126 # You can write your own handler to customise behaviour in more details.
2127 # User handler is specified with the full path starting with '/'.
2128 # This configuration option has an automatic default value.
2129 # thin_command = "lvm lvextend --use-policies"
2131 # Configuration option dmeventd/vdo_library.
2132 # The library dmeventd uses when monitoring a VDO pool device.
2133 # libdevmapper-event-lvm2vdo.so monitors the filling of a pool
2134 # and emits a warning through syslog when the usage exceeds 80%. The
2135 # warning is repeated when 85%, 90% and 95% of the pool is filled.
2136 # This configuration option has an automatic default value.
2137 # vdo_library = "libdevmapper-event-lvm2vdo.so"
2139 # Configuration option dmeventd/vdo_command.
2140 # The plugin runs command with each 5% increment when VDO pool volume
2142 # Command which starts with 'lvm ' prefix is internal lvm command.
2143 # You can write your own handler to customise behaviour in more details.
2144 # User handler is specified with the full path starting with '/'.
2145 # This configuration option has an automatic default value.
2146 # vdo_command = "lvm lvextend --use-policies"
2148 # Configuration option dmeventd/executable.
2149 # The full path to the dmeventd binary.
2150 # This configuration option has an automatic default value.
2151 # executable = "/sbin/dmeventd"
2154 # Configuration section tags.
2155 # Host tag settings.
2156 # This configuration section has an automatic default value.
2159 # Configuration option tags/hosttags.
2160 # Create a host tag using the machine name.
2161 # The machine name is nodename returned by uname(2).
2162 # This configuration option has an automatic default value.
2165 # Configuration section tags/<tag>.
2166 # Replace this subsection name with a custom tag name.
2167 # Multiple subsections like this can be created. The '@' prefix for
2168 # tags is optional. This subsection can contain host_list, which is a
2169 # list of machine names. If the name of the local machine is found in
2170 # host_list, then the name of this subsection is used as a tag and is
2171 # applied to the local machine as a 'host tag'. If this subsection is
2172 # empty (has no host_list), then the subsection name is always applied
2176 # The host tag foo is given to all hosts, and the host tag
2177 # bar is given to the hosts named machine1 and machine2.
2178 # tags { foo { } bar { host_list = [ "machine1", "machine2" ] } }
2180 # This configuration section has variable name.
2181 # This configuration section has an automatic default value.
2184 # Configuration option tags/<tag>/host_list.
2185 # A list of machine names.
2186 # These machine names are compared to the nodename returned
2187 # by uname(2). If the local machine name matches an entry in
2188 # this list, the name of the subsection is applied to the
2189 # machine as a 'host tag'.
2190 # This configuration option does not have a default value defined.