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.
111 # Configuration option devices/filter.
112 # Limit the block devices that are used by LVM commands.
113 # This is a list of regular expressions used to accept or reject block
114 # device path names. Each regex is delimited by a vertical bar '|'
115 # (or any character) and is preceded by 'a' to accept the path, or
116 # by 'r' to reject the path. The first regex in the list to match the
117 # path is used, producing the 'a' or 'r' result for the device.
118 # When multiple path names exist for a block device, if any path name
119 # matches an 'a' pattern before an 'r' pattern, then the device is
120 # accepted. If all the path names match an 'r' pattern first, then the
121 # device is rejected. Unmatching path names do not affect the accept
122 # or reject decision. If no path names for a device match a pattern,
123 # then the device is accepted. Be careful mixing 'a' and 'r' patterns,
124 # as the combination might produce unexpected results (test changes.)
125 # Run vgscan after changing the filter to regenerate the cache.
126 # See the use_lvmetad comment for a special case regarding filters.
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/sd[ab][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 and lvmetad.
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|.*/|" ]
154 # Configuration option devices/cache_dir.
155 # Directory in which to store the device cache file.
156 # The results of filtering are cached on disk to avoid rescanning dud
157 # devices (which can take a very long time). By default this cache is
158 # stored in a file named .cache. It is safe to delete this file; the
159 # tools regenerate it. If obtain_device_list_from_udev is enabled, the
160 # list of devices is obtained from udev and any existing .cache file
162 cache_dir = "/run/lvm"
164 # Configuration option devices/cache_file_prefix.
165 # A prefix used before the .cache file name. See devices/cache_dir.
166 cache_file_prefix = ""
168 # Configuration option devices/write_cache_state.
169 # Enable/disable writing the cache file. See devices/cache_dir.
170 write_cache_state = 1
172 # Configuration option devices/types.
173 # List of additional acceptable block device types.
174 # These are of device type names from /proc/devices, followed by the
175 # maximum number of partitions.
178 # types = [ "fd", 16 ]
180 # This configuration option is advanced.
181 # This configuration option does not have a default value defined.
183 # Configuration option devices/sysfs_scan.
184 # Restrict device scanning to block devices appearing in sysfs.
185 # This is a quick way of filtering out block devices that are not
186 # present on the system. sysfs must be part of the kernel and mounted.)
189 # Configuration option devices/multipath_component_detection.
190 # Ignore devices that are components of DM multipath devices.
191 multipath_component_detection = 1
193 # Configuration option devices/md_component_detection.
194 # Ignore devices that are components of software RAID (md) devices.
195 md_component_detection = 1
197 # Configuration option devices/fw_raid_component_detection.
198 # Ignore devices that are components of firmware RAID devices.
199 # LVM must use an external_device_info_source other than none for this
200 # detection to execute.
201 fw_raid_component_detection = 0
203 # Configuration option devices/md_chunk_alignment.
204 # Align PV data blocks with md device's stripe-width.
205 # This applies if a PV is placed directly on an md device.
206 md_chunk_alignment = 1
208 # Configuration option devices/default_data_alignment.
209 # Default alignment of the start of a PV data area in MB.
210 # If set to 0, a value of 64KiB will be used.
211 # Set to 1 for 1MiB, 2 for 2MiB, etc.
212 # This configuration option has an automatic default value.
213 # default_data_alignment = 1
215 # Configuration option devices/data_alignment_detection.
216 # Detect PV data alignment based on sysfs device information.
217 # The start of a PV data area will be a multiple of minimum_io_size or
218 # optimal_io_size exposed in sysfs. minimum_io_size is the smallest
219 # request the device can perform without incurring a read-modify-write
220 # penalty, e.g. MD chunk size. optimal_io_size is the device's
221 # preferred unit of receiving I/O, e.g. MD stripe width.
222 # minimum_io_size is used if optimal_io_size is undefined (0).
223 # If md_chunk_alignment is enabled, that detects the optimal_io_size.
224 # This setting takes precedence over md_chunk_alignment.
225 data_alignment_detection = 1
227 # Configuration option devices/data_alignment.
228 # Alignment of the start of a PV data area in KiB.
229 # If a PV is placed directly on an md device and md_chunk_alignment or
230 # data_alignment_detection are enabled, then this setting is ignored.
231 # Otherwise, md_chunk_alignment and data_alignment_detection are
232 # disabled if this is set. Set to 0 to use the default alignment or the
233 # page size, if larger.
236 # Configuration option devices/data_alignment_offset_detection.
237 # Detect PV data alignment offset based on sysfs device information.
238 # The start of a PV aligned data area will be shifted by the
239 # alignment_offset exposed in sysfs. This offset is often 0, but may
240 # be non-zero. Certain 4KiB sector drives that compensate for windows
241 # partitioning will have an alignment_offset of 3584 bytes (sector 7
242 # is the lowest aligned logical block, the 4KiB sectors start at
243 # LBA -1, and consequently sector 63 is aligned on a 4KiB boundary).
244 # pvcreate --dataalignmentoffset will skip this detection.
245 data_alignment_offset_detection = 1
247 # Configuration option devices/ignore_suspended_devices.
248 # Ignore DM devices that have I/O suspended while scanning devices.
249 # Otherwise, LVM waits for a suspended device to become accessible.
250 # This should only be needed in recovery situations.
251 ignore_suspended_devices = 0
253 # Configuration option devices/ignore_lvm_mirrors.
254 # Do not scan 'mirror' LVs to avoid possible deadlocks.
255 # This avoids possible deadlocks when using the 'mirror' segment type.
256 # This setting determines whether LVs using the 'mirror' segment type
257 # are scanned for LVM labels. This affects the ability of mirrors to
258 # be used as physical volumes. If this setting is enabled, it is
259 # impossible to create VGs on top of mirror LVs, i.e. to stack VGs on
260 # mirror LVs. If this setting is disabled, allowing mirror LVs to be
261 # scanned, it may cause LVM processes and I/O to the mirror to become
262 # blocked. This is due to the way that the mirror segment type handles
263 # failures. In order for the hang to occur, an LVM command must be run
264 # just after a failure and before the automatic LVM repair process
265 # takes place, or there must be failures in multiple mirrors in the
266 # same VG at the same time with write failures occurring moments before
267 # a scan of the mirror's labels. The 'mirror' scanning problems do not
268 # apply to LVM RAID types like 'raid1' which handle failures in a
269 # different way, making them a better choice for VG stacking.
270 ignore_lvm_mirrors = 1
272 # Configuration option devices/disable_after_error_count.
273 # Number of I/O errors after which a device is skipped.
274 # During each LVM operation, errors received from each device are
275 # counted. If the counter of a device exceeds the limit set here,
276 # no further I/O is sent to that device for the remainder of the
277 # operation. Setting this to 0 disables the counters altogether.
278 disable_after_error_count = 0
280 # Configuration option devices/require_restorefile_with_uuid.
281 # Allow use of pvcreate --uuid without requiring --restorefile.
282 require_restorefile_with_uuid = 1
284 # Configuration option devices/pv_min_size.
285 # Minimum size in KiB of block devices which can be used as PVs.
286 # In a clustered environment all nodes must use the same value.
287 # Any value smaller than 512KiB is ignored. The previous built-in
291 # Configuration option devices/issue_discards.
292 # Issue discards to PVs that are no longer used by an LV.
293 # Discards are sent to an LV's underlying physical volumes when the LV
294 # is no longer using the physical volumes' space, e.g. lvremove,
295 # lvreduce. Discards inform the storage that a region is no longer
296 # used. Storage that supports discards advertise the protocol-specific
297 # way discards should be issued by the kernel (TRIM, UNMAP, or
298 # WRITE SAME with UNMAP bit set). Not all storage will support or
299 # benefit from discards, but SSDs and thinly provisioned LUNs
300 # generally do. If enabled, discards will only be issued if both the
301 # storage and kernel provide support.
304 # Configuration option devices/allow_changes_with_duplicate_pvs.
305 # Allow VG modification while a PV appears on multiple devices.
306 # When a PV appears on multiple devices, LVM attempts to choose the
307 # best device to use for the PV. If the devices represent the same
308 # underlying storage, the choice has minimal consequence. If the
309 # devices represent different underlying storage, the wrong choice
310 # can result in data loss if the VG is modified. Disabling this
311 # setting is the safest option because it prevents modifying a VG
312 # or activating LVs in it while a PV appears on multiple devices.
313 # Enabling this setting allows the VG to be used as usual even with
315 allow_changes_with_duplicate_pvs = 0
318 # Configuration section allocation.
319 # How LVM selects space and applies properties to LVs.
322 # Configuration option allocation/cling_tag_list.
323 # Advise LVM which PVs to use when searching for new space.
324 # When searching for free space to extend an LV, the 'cling' allocation
325 # policy will choose space on the same PVs as the last segment of the
326 # existing LV. If there is insufficient space and a list of tags is
327 # defined here, it will check whether any of them are attached to the
328 # PVs concerned and then seek to match those PV tags between existing
329 # extents and new extents.
332 # Use the special tag "@*" as a wildcard to match any PV tag:
333 # cling_tag_list = [ "@*" ]
334 # LVs are mirrored between two sites within a single VG, and
335 # PVs are tagged with either @site1 or @site2 to indicate where
337 # cling_tag_list = [ "@site1", "@site2" ]
339 # This configuration option does not have a default value defined.
341 # Configuration option allocation/maximise_cling.
342 # Use a previous allocation algorithm.
343 # Changes made in version 2.02.85 extended the reach of the 'cling'
344 # policies to detect more situations where data can be grouped onto
345 # the same disks. This setting can be used to disable the changes
346 # and revert to the previous algorithm.
349 # Configuration option allocation/use_blkid_wiping.
350 # Use blkid to detect existing signatures on new PVs and LVs.
351 # The blkid library can detect more signatures than the native LVM
352 # detection code, but may take longer. LVM needs to be compiled with
353 # blkid wiping support for this setting to apply. LVM native detection
354 # code is currently able to recognize: MD device signatures,
355 # swap signature, and LUKS signatures. To see the list of signatures
356 # recognized by blkid, check the output of the 'blkid -k' command.
359 # Configuration option allocation/wipe_signatures_when_zeroing_new_lvs.
360 # Look for and erase any signatures while zeroing a new LV.
361 # The --wipesignatures option overrides this setting.
362 # Zeroing is controlled by the -Z/--zero option, and if not specified,
363 # zeroing is used by default if possible. Zeroing simply overwrites the
364 # first 4KiB of a new LV with zeroes and does no signature detection or
365 # wiping. Signature wiping goes beyond zeroing and detects exact types
366 # and positions of signatures within the whole LV. It provides a
367 # cleaner LV after creation as all known signatures are wiped. The LV
368 # is not claimed incorrectly by other tools because of old signatures
369 # from previous use. The number of signatures that LVM can detect
370 # depends on the detection code that is selected (see
371 # use_blkid_wiping.) Wiping each detected signature must be confirmed.
372 # When this setting is disabled, signatures on new LVs are not detected
373 # or erased unless the --wipesignatures option is used directly.
374 wipe_signatures_when_zeroing_new_lvs = 1
376 # Configuration option allocation/mirror_logs_require_separate_pvs.
377 # Mirror logs and images will always use different PVs.
378 # The default setting changed in version 2.02.85.
379 mirror_logs_require_separate_pvs = 0
381 # Configuration option allocation/raid_stripe_all_devices.
382 # Stripe across all PVs when RAID stripes are not specified.
383 # If enabled, all PVs in the VG or on the command line are used for raid0/4/5/6/10
384 # when the command does not specify the number of stripes to use.
385 # This was the default behaviour until release 2.02.162.
386 # This configuration option has an automatic default value.
387 # raid_stripe_all_devices = 0
389 # Configuration option allocation/cache_pool_metadata_require_separate_pvs.
390 # Cache pool metadata and data will always use different PVs.
391 cache_pool_metadata_require_separate_pvs = 0
393 # Configuration option allocation/cache_mode.
394 # The default cache mode used for new cache.
398 # Data blocks are immediately written from the cache to disk.
400 # Data blocks are written from the cache back to disk after some
401 # delay to improve performance.
403 # This setting replaces allocation/cache_pool_cachemode.
404 # This configuration option has an automatic default value.
405 # cache_mode = "writethrough"
407 # Configuration option allocation/cache_policy.
408 # The default cache policy used for new cache volume.
409 # Since kernel 4.2 the default policy is smq (Stochastic multique),
410 # otherwise the older mq (Multiqueue) policy is selected.
411 # This configuration option does not have a default value defined.
413 # Configuration section allocation/cache_settings.
414 # Settings for the cache policy.
415 # See documentation for individual cache policies for more info.
416 # This configuration section has an automatic default value.
420 # Configuration option allocation/cache_pool_chunk_size.
421 # The minimal chunk size in KiB for cache pool volumes.
422 # Using a chunk_size that is too large can result in wasteful use of
423 # the cache, where small reads and writes can cause large sections of
424 # an LV to be mapped into the cache. However, choosing a chunk_size
425 # that is too small can result in more overhead trying to manage the
426 # numerous chunks that become mapped into the cache. The former is
427 # more of a problem than the latter in most cases, so the default is
428 # on the smaller end of the spectrum. Supported values range from
429 # 32KiB to 1GiB in multiples of 32.
430 # This configuration option does not have a default value defined.
432 # Configuration option allocation/cache_pool_max_chunks.
433 # The maximum number of chunks in a cache pool.
434 # For cache target v1.9 the recommended maximumm is 1000000 chunks.
435 # Using cache pool with more chunks may degrade cache performance.
436 # This configuration option does not have a default value defined.
438 # Configuration option allocation/thin_pool_metadata_require_separate_pvs.
439 # Thin pool metdata and data will always use different PVs.
440 thin_pool_metadata_require_separate_pvs = 0
442 # Configuration option allocation/thin_pool_zero.
443 # Thin pool data chunks are zeroed before they are first used.
444 # Zeroing with a larger thin pool chunk size reduces performance.
445 # This configuration option has an automatic default value.
448 # Configuration option allocation/thin_pool_discards.
449 # The discards behaviour of thin pool volumes.
456 # This configuration option has an automatic default value.
457 # thin_pool_discards = "passdown"
459 # Configuration option allocation/thin_pool_chunk_size_policy.
460 # The chunk size calculation policy for thin pool volumes.
464 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
465 # the chunk size based on estimation and device hints exposed in
466 # sysfs - the minimum_io_size. The chunk size is always at least
469 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
470 # the chunk size for performance based on device hints exposed in
471 # sysfs - the optimal_io_size. The chunk size is always at least
474 # This configuration option has an automatic default value.
475 # thin_pool_chunk_size_policy = "generic"
477 # Configuration option allocation/thin_pool_chunk_size.
478 # The minimal chunk size in KiB for thin pool volumes.
479 # Larger chunk sizes may improve performance for plain thin volumes,
480 # however using them for snapshot volumes is less efficient, as it
481 # consumes more space and takes extra time for copying. When unset,
482 # lvm tries to estimate chunk size starting from 64KiB. Supported
483 # values are in the range 64KiB to 1GiB.
484 # This configuration option does not have a default value defined.
486 # Configuration option allocation/physical_extent_size.
487 # Default physical extent size in KiB to use for new VGs.
488 # This configuration option has an automatic default value.
489 # physical_extent_size = 4096
492 # Configuration section log.
493 # How LVM log information is reported.
496 # Configuration option log/report_command_log.
497 # Enable or disable LVM log reporting.
498 # If enabled, LVM will collect a log of operations, messages,
499 # per-object return codes with object identification and associated
500 # error numbers (errnos) during LVM command processing. Then the
501 # log is either reported solely or in addition to any existing
502 # reports, depending on LVM command used. If it is a reporting command
503 # (e.g. pvs, vgs, lvs, lvm fullreport), then the log is reported in
504 # addition to any existing reports. Otherwise, there's only log report
505 # on output. For all applicable LVM commands, you can request that
506 # the output has only log report by using --logonly command line
507 # option. Use log/command_log_cols and log/command_log_sort settings
508 # to define fields to display and sort fields for the log report.
509 # You can also use log/command_log_selection to define selection
510 # criteria used each time the log is reported.
511 # This configuration option has an automatic default value.
512 # report_command_log = 0
514 # Configuration option log/command_log_sort.
515 # List of columns to sort by when reporting command log.
516 # See <lvm command> --logonly --configreport log -o help
517 # for the list of possible fields.
518 # This configuration option has an automatic default value.
519 # command_log_sort = "log_seq_num"
521 # Configuration option log/command_log_cols.
522 # List of columns to report when reporting command log.
523 # See <lvm command> --logonly --configreport log -o help
524 # for the list of possible fields.
525 # This configuration option has an automatic default value.
526 # 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"
528 # Configuration option log/command_log_selection.
529 # Selection criteria used when reporting command log.
530 # You can define selection criteria that are applied each
531 # time log is reported. This way, it is possible to control the
532 # amount of log that is displayed on output and you can select
533 # only parts of the log that are important for you. To define
534 # selection criteria, use fields from log report. See also
535 # <lvm command> --logonly --configreport log -S help for the
536 # list of possible fields and selection operators. You can also
537 # define selection criteria for log report on command line directly
538 # using <lvm command> --configreport log -S <selection criteria>
539 # which has precedence over log/command_log_selection setting.
540 # For more information about selection criteria in general, see
542 # This configuration option has an automatic default value.
543 # command_log_selection = "!(log_type=status && message=success)"
545 # Configuration option log/verbose.
546 # Controls the messages sent to stdout or stderr.
549 # Configuration option log/silent.
550 # Suppress all non-essential messages from stdout.
551 # This has the same effect as -qq. When enabled, the following commands
552 # still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck,
553 # pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs.
554 # Non-essential messages are shifted from log level 4 to log level 5
555 # for syslog and lvm2_log_fn purposes.
556 # Any 'yes' or 'no' questions not overridden by other arguments are
557 # suppressed and default to 'no'.
560 # Configuration option log/syslog.
561 # Send log messages through syslog.
564 # Configuration option log/file.
565 # Write error and debug log messages to a file specified here.
566 # This configuration option does not have a default value defined.
568 # Configuration option log/overwrite.
569 # Overwrite the log file each time the program is run.
572 # Configuration option log/level.
573 # The level of log messages that are sent to the log file or syslog.
574 # There are 6 syslog-like log levels currently in use: 2 to 7 inclusive.
575 # 7 is the most verbose (LOG_DEBUG).
578 # Configuration option log/indent.
579 # Indent messages according to their severity.
582 # Configuration option log/command_names.
583 # Display the command name on each line of output.
586 # Configuration option log/prefix.
587 # A prefix to use before the log message text.
588 # (After the command name, if selected).
589 # Two spaces allows you to see/grep the severity of each message.
590 # To make the messages look similar to the original LVM tools use:
591 # indent = 0, command_names = 1, prefix = " -- "
594 # Configuration option log/activation.
595 # Log messages during activation.
596 # Don't use this in low memory situations (can deadlock).
599 # Configuration option log/debug_classes.
600 # Select log messages by class.
601 # Some debugging messages are assigned to a class and only appear in
602 # debug output if the class is listed here. Classes currently
603 # available: memory, devices, activation, allocation, lvmetad,
604 # metadata, cache, locking, lvmpolld. Use "all" to see everything.
605 debug_classes = [ "memory", "devices", "activation", "allocation", "lvmetad", "metadata", "cache", "locking", "lvmpolld", "dbus" ]
608 # Configuration section backup.
609 # How LVM metadata is backed up and archived.
610 # In LVM, a 'backup' is a copy of the metadata for the current system,
611 # and an 'archive' contains old metadata configurations. They are
612 # stored in a human readable text format.
615 # Configuration option backup/backup.
616 # Maintain a backup of the current metadata configuration.
617 # Think very hard before turning this off!
620 # Configuration option backup/backup_dir.
621 # Location of the metadata backup files.
622 # Remember to back up this directory regularly!
623 backup_dir = "/etc/lvm/backup"
625 # Configuration option backup/archive.
626 # Maintain an archive of old metadata configurations.
627 # Think very hard before turning this off.
630 # Configuration option backup/archive_dir.
631 # Location of the metdata archive files.
632 # Remember to back up this directory regularly!
633 archive_dir = "/etc/lvm/archive"
635 # Configuration option backup/retain_min.
636 # Minimum number of archives to keep.
639 # Configuration option backup/retain_days.
640 # Minimum number of days to keep archive files.
644 # Configuration section shell.
645 # Settings for running LVM in shell (readline) mode.
648 # Configuration option shell/history_size.
649 # Number of lines of history to store in ~/.lvm_history.
653 # Configuration section global.
654 # Miscellaneous global LVM settings.
657 # Configuration option global/umask.
658 # The file creation mask for any files and directories created.
659 # Interpreted as octal if the first digit is zero.
662 # Configuration option global/test.
663 # No on-disk metadata changes will be made in test mode.
664 # Equivalent to having the -t option on every command.
667 # Configuration option global/units.
668 # Default value for --units argument.
671 # Configuration option global/si_unit_consistency.
672 # Distinguish between powers of 1024 and 1000 bytes.
673 # The LVM commands distinguish between powers of 1024 bytes,
674 # e.g. KiB, MiB, GiB, and powers of 1000 bytes, e.g. KB, MB, GB.
675 # If scripts depend on the old behaviour, disable this setting
676 # temporarily until they are updated.
677 si_unit_consistency = 1
679 # Configuration option global/suffix.
680 # Display unit suffix for sizes.
681 # This setting has no effect if the units are in human-readable form
682 # (global/units = "h") in which case the suffix is always displayed.
685 # Configuration option global/activation.
686 # Enable/disable communication with the kernel device-mapper.
687 # Disable to use the tools to manipulate LVM metadata without
688 # activating any logical volumes. If the device-mapper driver
689 # is not present in the kernel, disabling this should suppress
690 # the error messages.
693 # Configuration option global/fallback_to_lvm1.
694 # Try running LVM1 tools if LVM cannot communicate with DM.
695 # This option only applies to 2.4 kernels and is provided to help
696 # switch between device-mapper kernels and LVM1 kernels. The LVM1
697 # tools need to be installed with .lvm1 suffices, e.g. vgscan.lvm1.
698 # They will stop working once the lvm2 on-disk metadata format is used.
699 # This configuration option has an automatic default value.
700 # fallback_to_lvm1 = 0
702 # Configuration option global/format.
703 # The default metadata format that commands should use.
704 # The -M 1|2 option overrides this setting.
710 # This configuration option has an automatic default value.
713 # Configuration option global/format_libraries.
714 # Shared libraries that process different metadata formats.
715 # If support for LVM1 metadata was compiled as a shared library use
716 # format_libraries = "liblvm2format1.so"
717 # This configuration option does not have a default value defined.
719 # Configuration option global/segment_libraries.
720 # This configuration option does not have a default value defined.
722 # Configuration option global/proc.
723 # Location of proc filesystem.
724 # This configuration option is advanced.
727 # Configuration option global/etc.
728 # Location of /etc system configuration directory.
731 # Configuration option global/locking_type.
732 # Type of locking to use.
736 # Turns off locking. Warning: this risks metadata corruption if
737 # commands run concurrently.
739 # LVM uses local file-based locking, the standard mode.
741 # LVM uses the external shared library locking_library.
743 # LVM uses built-in clustered locking with clvmd.
744 # This is incompatible with lvmetad. If use_lvmetad is enabled,
745 # LVM prints a warning and disables lvmetad use.
747 # LVM uses read-only locking which forbids any operations that
748 # might change metadata.
750 # Offers dummy locking for tools that do not need any locks.
751 # You should not need to set this directly; the tools will select
752 # when to use it instead of the configured locking_type.
753 # Do not use lvmetad or the kernel device-mapper driver with this
754 # locking type. It is used by the --readonly option that offers
755 # read-only access to Volume Group metadata that cannot be locked
756 # safely because it belongs to an inaccessible domain and might be
757 # in use, for example a virtual machine image or a disk that is
758 # shared by a clustered machine.
762 # Configuration option global/wait_for_locks.
763 # When disabled, fail if a lock request would block.
766 # Configuration option global/fallback_to_clustered_locking.
767 # Attempt to use built-in cluster locking if locking_type 2 fails.
768 # If using external locking (type 2) and initialisation fails, with
769 # this enabled, an attempt will be made to use the built-in clustered
770 # locking. Disable this if using a customised locking_library.
771 fallback_to_clustered_locking = 1
773 # Configuration option global/fallback_to_local_locking.
774 # Use locking_type 1 (local) if locking_type 2 or 3 fail.
775 # If an attempt to initialise type 2 or type 3 locking failed, perhaps
776 # because cluster components such as clvmd are not running, with this
777 # enabled, an attempt will be made to use local file-based locking
778 # (type 1). If this succeeds, only commands against local VGs will
779 # proceed. VGs marked as clustered will be ignored.
780 fallback_to_local_locking = 1
782 # Configuration option global/locking_dir.
783 # Directory to use for LVM command file locks.
784 # Local non-LV directory that holds file-based locks while commands are
785 # in progress. A directory like /tmp that may get wiped on reboot is OK.
786 locking_dir = "/run/lock/lvm"
788 # Configuration option global/prioritise_write_locks.
789 # Allow quicker VG write access during high volume read access.
790 # When there are competing read-only and read-write access requests for
791 # a volume group's metadata, instead of always granting the read-only
792 # requests immediately, delay them to allow the read-write requests to
793 # be serviced. Without this setting, write access may be stalled by a
794 # high volume of read-only requests. This option only affects
795 # locking_type 1 viz. local file-based locking.
796 prioritise_write_locks = 1
798 # Configuration option global/library_dir.
799 # Search this directory first for shared libraries.
800 # This configuration option does not have a default value defined.
802 # Configuration option global/locking_library.
803 # The external locking library to use for locking_type 2.
804 # This configuration option has an automatic default value.
805 # locking_library = "liblvm2clusterlock.so"
807 # Configuration option global/abort_on_internal_errors.
808 # Abort a command that encounters an internal error.
809 # Treat any internal errors as fatal errors, aborting the process that
810 # encountered the internal error. Please only enable for debugging.
811 abort_on_internal_errors = 0
813 # Configuration option global/detect_internal_vg_cache_corruption.
814 # Internal verification of VG structures.
815 # Check if CRC matches when a parsed VG is used multiple times. This
816 # is useful to catch unexpected changes to cached VG structures.
817 # Please only enable for debugging.
818 detect_internal_vg_cache_corruption = 0
820 # Configuration option global/metadata_read_only.
821 # No operations that change on-disk metadata are permitted.
822 # Additionally, read-only commands that encounter metadata in need of
823 # repair will still be allowed to proceed exactly as if the repair had
824 # been performed (except for the unchanged vg_seqno). Inappropriate
825 # use could mess up your system, so seek advice first!
826 metadata_read_only = 0
828 # Configuration option global/mirror_segtype_default.
829 # The segment type used by the short mirroring option -m.
830 # The --type mirror|raid1 option overrides this setting.
834 # The original RAID1 implementation from LVM/DM. It is
835 # characterized by a flexible log solution (core, disk, mirrored),
836 # and by the necessity to block I/O while handling a failure.
837 # There is an inherent race in the dmeventd failure handling logic
838 # with snapshots of devices using this type of RAID1 that in the
839 # worst case could cause a deadlock. (Also see
840 # devices/ignore_lvm_mirrors.)
842 # This is a newer RAID1 implementation using the MD RAID1
843 # personality through device-mapper. It is characterized by a
844 # lack of log options. (A log is always allocated for every
845 # device and they are placed on the same device as the image,
846 # so no separate devices are required.) This mirror
847 # implementation does not require I/O to be blocked while
848 # handling a failure. This mirror implementation is not
849 # cluster-aware and cannot be used in a shared (active/active)
850 # fashion in a cluster.
852 mirror_segtype_default = "raid1"
854 # Configuration option global/raid10_segtype_default.
855 # The segment type used by the -i -m combination.
856 # The --type raid10|mirror option overrides this setting.
857 # The --stripes/-i and --mirrors/-m options can both be specified
858 # during the creation of a logical volume to use both striping and
859 # mirroring for the LV. There are two different implementations.
863 # LVM uses MD's RAID10 personality through DM. This is the
866 # LVM layers the 'mirror' and 'stripe' segment types. The layering
867 # is done by creating a mirror LV on top of striped sub-LVs,
868 # effectively creating a RAID 0+1 array. The layering is suboptimal
869 # in terms of providing redundancy and performance.
871 raid10_segtype_default = "raid10"
873 # Configuration option global/sparse_segtype_default.
874 # The segment type used by the -V -L combination.
875 # The --type snapshot|thin option overrides this setting.
876 # The combination of -V and -L options creates a sparse LV. There are
877 # two different implementations.
881 # The original snapshot implementation from LVM/DM. It uses an old
882 # snapshot that mixes data and metadata within a single COW
883 # storage volume and performs poorly when the size of stored data
884 # passes hundreds of MB.
886 # A newer implementation that uses thin provisioning. It has a
887 # bigger minimal chunk size (64KiB) and uses a separate volume for
888 # metadata. It has better performance, especially when more data
889 # is used. It also supports full snapshots.
891 sparse_segtype_default = "thin"
893 # Configuration option global/lvdisplay_shows_full_device_path.
894 # Enable this to reinstate the previous lvdisplay name format.
895 # The default format for displaying LV names in lvdisplay was changed
896 # in version 2.02.89 to show the LV name and path separately.
897 # Previously this was always shown as /dev/vgname/lvname even when that
898 # was never a valid path in the /dev filesystem.
899 # This configuration option has an automatic default value.
900 # lvdisplay_shows_full_device_path = 0
902 # Configuration option global/use_lvmetad.
903 # Use lvmetad to cache metadata and reduce disk scanning.
904 # When enabled (and running), lvmetad provides LVM commands with VG
905 # metadata and PV state. LVM commands then avoid reading this
906 # information from disks which can be slow. When disabled (or not
907 # running), LVM commands fall back to scanning disks to obtain VG
908 # metadata. lvmetad is kept updated via udev rules which must be set
909 # up for LVM to work correctly. (The udev rules should be installed
910 # by default.) Without a proper udev setup, changes in the system's
911 # block device configuration will be unknown to LVM, and ignored
912 # until a manual 'pvscan --cache' is run. If lvmetad was running
913 # while use_lvmetad was disabled, it must be stopped, use_lvmetad
914 # enabled, and then started. When using lvmetad, LV activation is
915 # switched to an automatic, event-based mode. In this mode, LVs are
916 # activated based on incoming udev events that inform lvmetad when
917 # PVs appear on the system. When a VG is complete (all PVs present),
918 # it is auto-activated. The auto_activation_volume_list setting
919 # controls which LVs are auto-activated (all by default.)
920 # When lvmetad is updated (automatically by udev events, or directly
921 # by pvscan --cache), devices/filter is ignored and all devices are
922 # scanned by default. lvmetad always keeps unfiltered information
923 # which is provided to LVM commands. Each LVM command then filters
924 # based on devices/filter. This does not apply to other, non-regexp,
925 # filtering settings: component filters such as multipath and MD
926 # are checked during pvscan --cache. To filter a device and prevent
927 # scanning from the LVM system entirely, including lvmetad, use
928 # devices/global_filter.
931 # Configuration option global/lvmetad_update_wait_time.
932 # The number of seconds a command will wait for lvmetad update to finish.
933 # After waiting for this period, a command will not use lvmetad, and
934 # will revert to disk scanning.
935 # This configuration option has an automatic default value.
936 # lvmetad_update_wait_time = 10
938 # Configuration option global/use_lvmlockd.
939 # Use lvmlockd for locking among hosts using LVM on shared storage.
940 # Applicable only if LVM is compiled with lockd support in which
941 # case there is also lvmlockd(8) man page available for more
945 # Configuration option global/lvmlockd_lock_retries.
946 # Retry lvmlockd lock requests this many times.
947 # Applicable only if LVM is compiled with lockd support
948 # This configuration option has an automatic default value.
949 # lvmlockd_lock_retries = 3
951 # Configuration option global/sanlock_lv_extend.
952 # Size in MiB to extend the internal LV holding sanlock locks.
953 # The internal LV holds locks for each LV in the VG, and after enough
954 # LVs have been created, the internal LV needs to be extended. lvcreate
955 # will automatically extend the internal LV when needed by the amount
956 # specified here. Setting this to 0 disables the automatic extension
957 # and can cause lvcreate to fail. Applicable only if LVM is compiled
959 # This configuration option has an automatic default value.
960 # sanlock_lv_extend = 256
962 # Configuration option global/thin_check_executable.
963 # The full path to the thin_check command.
964 # LVM uses this command to check that a thin metadata device is in a
965 # usable state. When a thin pool is activated and after it is
966 # deactivated, this command is run. Activation will only proceed if
967 # the command has an exit status of 0. Set to "" to skip this check.
968 # (Not recommended.) Also see thin_check_options.
969 # (See package device-mapper-persistent-data or thin-provisioning-tools)
970 # This configuration option has an automatic default value.
971 # thin_check_executable = "/usr/sbin/thin_check"
973 # Configuration option global/thin_dump_executable.
974 # The full path to the thin_dump command.
975 # LVM uses this command to dump thin pool metadata.
976 # (See package device-mapper-persistent-data or thin-provisioning-tools)
977 # This configuration option has an automatic default value.
978 # thin_dump_executable = "/usr/sbin/thin_dump"
980 # Configuration option global/thin_repair_executable.
981 # The full path to the thin_repair command.
982 # LVM uses this command to repair a thin metadata device if it is in
983 # an unusable state. Also see thin_repair_options.
984 # (See package device-mapper-persistent-data or thin-provisioning-tools)
985 # This configuration option has an automatic default value.
986 # thin_repair_executable = "/usr/sbin/thin_repair"
988 # Configuration option global/thin_check_options.
989 # List of options passed to the thin_check command.
990 # With thin_check version 2.1 or newer you can add the option
991 # --ignore-non-fatal-errors to let it pass through ignorable errors
992 # and fix them later. With thin_check version 3.2 or newer you should
993 # include the option --clear-needs-check-flag.
994 # This configuration option has an automatic default value.
995 # thin_check_options = [ "-q", "--clear-needs-check-flag" ]
997 # Configuration option global/thin_repair_options.
998 # List of options passed to the thin_repair command.
999 # This configuration option has an automatic default value.
1000 # thin_repair_options = [ "" ]
1002 # Configuration option global/thin_disabled_features.
1003 # Features to not use in the thin driver.
1004 # This can be helpful for testing, or to avoid using a feature that is
1005 # causing problems. Features include: block_size, discards,
1006 # discards_non_power_2, external_origin, metadata_resize,
1007 # external_origin_extend, error_if_no_space.
1010 # thin_disabled_features = [ "discards", "block_size" ]
1012 # This configuration option does not have a default value defined.
1014 # Configuration option global/cache_disabled_features.
1015 # Features to not use in the cache driver.
1016 # This can be helpful for testing, or to avoid using a feature that is
1017 # causing problems. Features include: policy_mq, policy_smq.
1020 # cache_disabled_features = [ "policy_smq" ]
1022 # This configuration option does not have a default value defined.
1024 # Configuration option global/cache_check_executable.
1025 # The full path to the cache_check command.
1026 # LVM uses this command to check that a cache metadata device is in a
1027 # usable state. When a cached LV is activated and after it is
1028 # deactivated, this command is run. Activation will only proceed if the
1029 # command has an exit status of 0. Set to "" to skip this check.
1030 # (Not recommended.) Also see cache_check_options.
1031 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1032 # This configuration option has an automatic default value.
1033 # cache_check_executable = "/usr/sbin/cache_check"
1035 # Configuration option global/cache_dump_executable.
1036 # The full path to the cache_dump command.
1037 # LVM uses this command to dump cache pool metadata.
1038 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1039 # This configuration option has an automatic default value.
1040 # cache_dump_executable = "/usr/sbin/cache_dump"
1042 # Configuration option global/cache_repair_executable.
1043 # The full path to the cache_repair command.
1044 # LVM uses this command to repair a cache metadata device if it is in
1045 # an unusable state. Also see cache_repair_options.
1046 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1047 # This configuration option has an automatic default value.
1048 # cache_repair_executable = "/usr/sbin/cache_repair"
1050 # Configuration option global/cache_check_options.
1051 # List of options passed to the cache_check command.
1052 # With cache_check version 5.0 or newer you should include the option
1053 # --clear-needs-check-flag.
1054 # This configuration option has an automatic default value.
1055 # cache_check_options = [ "-q", "--clear-needs-check-flag" ]
1057 # Configuration option global/cache_repair_options.
1058 # List of options passed to the cache_repair command.
1059 # This configuration option has an automatic default value.
1060 # cache_repair_options = [ "" ]
1062 # Configuration option global/system_id_source.
1063 # The method LVM uses to set the local system ID.
1064 # Volume Groups can also be given a system ID (by vgcreate, vgchange,
1065 # or vgimport.) A VG on shared storage devices is accessible only to
1066 # the host with a matching system ID. See 'man lvmsystemid' for
1067 # information on limitations and correct usage.
1071 # The host has no system ID.
1073 # Obtain the system ID from the system_id setting in the 'local'
1074 # section of an lvm configuration file, e.g. lvmlocal.conf.
1076 # Set the system ID from the hostname (uname) of the system.
1077 # System IDs beginning localhost are not permitted.
1079 # Use the contents of the machine-id file to set the system ID.
1080 # Some systems create this file at installation time.
1081 # See 'man machine-id' and global/etc.
1083 # Use the contents of another file (system_id_file) to set the
1086 system_id_source = "none"
1088 # Configuration option global/system_id_file.
1089 # The full path to the file containing a system ID.
1090 # This is used when system_id_source is set to 'file'.
1091 # Comments starting with the character # are ignored.
1092 # This configuration option does not have a default value defined.
1094 # Configuration option global/use_lvmpolld.
1095 # Use lvmpolld to supervise long running LVM commands.
1096 # When enabled, control of long running LVM commands is transferred
1097 # from the original LVM command to the lvmpolld daemon. This allows
1098 # the operation to continue independent of the original LVM command.
1099 # After lvmpolld takes over, the LVM command displays the progress
1100 # of the ongoing operation. lvmpolld itself runs LVM commands to
1101 # manage the progress of ongoing operations. lvmpolld can be used as
1102 # a native systemd service, which allows it to be started on demand,
1103 # and to use its own control group. When this option is disabled, LVM
1104 # commands will supervise long running operations by forking themselves.
1105 # Applicable only if LVM is compiled with lvmpolld support.
1108 # Configuration option global/notify_dbus.
1109 # Enable D-Bus notification from LVM commands.
1110 # When enabled, an LVM command that changes PVs, changes VG metadata,
1111 # or changes the activation state of an LV will send a notification.
1115 # Configuration section activation.
1118 # Configuration option activation/checks.
1119 # Perform internal checks of libdevmapper operations.
1120 # Useful for debugging problems with activation. Some of the checks may
1121 # be expensive, so it's best to use this only when there seems to be a
1125 # Configuration option activation/udev_sync.
1126 # Use udev notifications to synchronize udev and LVM.
1127 # The --nodevsync option overrides this setting.
1128 # When disabled, LVM commands will not wait for notifications from
1129 # udev, but continue irrespective of any possible udev processing in
1130 # the background. Only use this if udev is not running or has rules
1131 # that ignore the devices LVM creates. If enabled when udev is not
1132 # running, and LVM processes are waiting for udev, run the command
1133 # 'dmsetup udevcomplete_all' to wake them up.
1136 # Configuration option activation/udev_rules.
1137 # Use udev rules to manage LV device nodes and symlinks.
1138 # When disabled, LVM will manage the device nodes and symlinks for
1139 # active LVs itself. Manual intervention may be required if this
1140 # setting is changed while LVs are active.
1143 # Configuration option activation/verify_udev_operations.
1144 # Use extra checks in LVM to verify udev operations.
1145 # This enables additional checks (and if necessary, repairs) on entries
1146 # in the device directory after udev has completed processing its
1147 # events. Useful for diagnosing problems with LVM/udev interactions.
1148 verify_udev_operations = 0
1150 # Configuration option activation/retry_deactivation.
1151 # Retry failed LV deactivation.
1152 # If LV deactivation fails, LVM will retry for a few seconds before
1153 # failing. This may happen because a process run from a quick udev rule
1154 # temporarily opened the device.
1155 retry_deactivation = 1
1157 # Configuration option activation/missing_stripe_filler.
1158 # Method to fill missing stripes when activating an incomplete LV.
1159 # Using 'error' will make inaccessible parts of the device return I/O
1160 # errors on access. You can instead use a device path, in which case,
1161 # that device will be used in place of missing stripes. Using anything
1162 # other than 'error' with mirrored or snapshotted volumes is likely to
1163 # result in data corruption.
1164 # This configuration option is advanced.
1165 missing_stripe_filler = "error"
1167 # Configuration option activation/use_linear_target.
1168 # Use the linear target to optimize single stripe LVs.
1169 # When disabled, the striped target is used. The linear target is an
1170 # optimised version of the striped target that only handles a single
1172 use_linear_target = 1
1174 # Configuration option activation/reserved_stack.
1175 # Stack size in KiB to reserve for use while devices are suspended.
1176 # Insufficent reserve risks I/O deadlock during device suspension.
1179 # Configuration option activation/reserved_memory.
1180 # Memory size in KiB to reserve for use while devices are suspended.
1181 # Insufficent reserve risks I/O deadlock during device suspension.
1182 reserved_memory = 8192
1184 # Configuration option activation/process_priority.
1185 # Nice value used while devices are suspended.
1186 # Use a high priority so that LVs are suspended
1187 # for the shortest possible time.
1188 process_priority = -18
1190 # Configuration option activation/volume_list.
1191 # Only LVs selected by this list are activated.
1192 # If this list is defined, an LV is only activated if it matches an
1193 # entry in this list. If this list is undefined, it imposes no limits
1194 # on LV activation (all are allowed).
1198 # The VG name is matched exactly and selects all LVs in the VG.
1200 # The VG name and LV name are matched exactly and selects the LV.
1202 # Selects an LV if the specified tag matches a tag set on the LV
1205 # Selects an LV if a tag defined on the host is also set on the LV
1206 # or VG. See tags/hosttags. If any host tags exist but volume_list
1207 # is not defined, a default single-entry list containing '@*'
1211 # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1213 # This configuration option does not have a default value defined.
1215 # Configuration option activation/auto_activation_volume_list.
1216 # Only LVs selected by this list are auto-activated.
1217 # This list works like volume_list, but it is used only by
1218 # auto-activation commands. It does not apply to direct activation
1219 # commands. If this list is defined, an LV is only auto-activated
1220 # if it matches an entry in this list. If this list is undefined, it
1221 # imposes no limits on LV auto-activation (all are allowed.) If this
1222 # list is defined and empty, i.e. "[]", then no LVs are selected for
1223 # auto-activation. An LV that is selected by this list for
1224 # auto-activation, must also be selected by volume_list (if defined)
1225 # before it is activated. Auto-activation is an activation command that
1226 # includes the 'a' argument: --activate ay or -a ay. The 'a' (auto)
1227 # argument for auto-activation is meant to be used by activation
1228 # commands that are run automatically by the system, as opposed to LVM
1229 # commands run directly by a user. A user may also use the 'a' flag
1230 # directly to perform auto-activation. Also see pvscan(8) for more
1231 # information about auto-activation.
1235 # The VG name is matched exactly and selects all LVs in the VG.
1237 # The VG name and LV name are matched exactly and selects the LV.
1239 # Selects an LV if the specified tag matches a tag set on the LV
1242 # Selects an LV if a tag defined on the host is also set on the LV
1243 # or VG. See tags/hosttags. If any host tags exist but volume_list
1244 # is not defined, a default single-entry list containing '@*'
1248 # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1250 # This configuration option does not have a default value defined.
1252 # Configuration option activation/read_only_volume_list.
1253 # LVs in this list are activated in read-only mode.
1254 # If this list is defined, each LV that is to be activated is checked
1255 # against this list, and if it matches, it is activated in read-only
1256 # mode. This overrides the permission setting stored in the metadata,
1257 # e.g. from --permission rw.
1261 # The VG name is matched exactly and selects all LVs in the VG.
1263 # The VG name and LV name are matched exactly and selects the LV.
1265 # Selects an LV if the specified tag matches a tag set on the LV
1268 # Selects an LV if a tag defined on the host is also set on the LV
1269 # or VG. See tags/hosttags. If any host tags exist but volume_list
1270 # is not defined, a default single-entry list containing '@*'
1274 # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1276 # This configuration option does not have a default value defined.
1278 # Configuration option activation/raid_region_size.
1279 # Size in KiB of each raid or mirror synchronization region.
1280 # For raid or mirror segment types, this is the amount of data that is
1281 # copied at once when initializing, or moved at once by pvmove.
1282 raid_region_size = 512
1284 # Configuration option activation/error_when_full.
1285 # Return errors if a thin pool runs out of space.
1286 # The --errorwhenfull option overrides this setting.
1287 # When enabled, writes to thin LVs immediately return an error if the
1288 # thin pool is out of data space. When disabled, writes to thin LVs
1289 # are queued if the thin pool is out of space, and processed when the
1290 # thin pool data space is extended. New thin pools are assigned the
1291 # behavior defined here.
1292 # This configuration option has an automatic default value.
1293 # error_when_full = 0
1295 # Configuration option activation/readahead.
1296 # Setting to use when there is no readahead setting in metadata.
1300 # Disable readahead.
1302 # Use default value chosen by kernel.
1306 # Configuration option activation/raid_fault_policy.
1307 # Defines how a device failure in a RAID LV is handled.
1308 # This includes LVs that have the following segment types:
1309 # raid1, raid4, raid5*, and raid6*.
1310 # If a device in the LV fails, the policy determines the steps
1311 # performed by dmeventd automatically, and the steps perfomed by the
1312 # manual command lvconvert --repair --use-policies.
1313 # Automatic handling requires dmeventd to be monitoring the LV.
1317 # Use the system log to warn the user that a device in the RAID LV
1318 # has failed. It is left to the user to run lvconvert --repair
1319 # manually to remove or replace the failed device. As long as the
1320 # number of failed devices does not exceed the redundancy of the LV
1321 # (1 device for raid4/5, 2 for raid6), the LV will remain usable.
1323 # Attempt to use any extra physical volumes in the VG as spares and
1324 # replace faulty devices.
1326 raid_fault_policy = "warn"
1328 # Configuration option activation/mirror_image_fault_policy.
1329 # Defines how a device failure in a 'mirror' LV is handled.
1330 # An LV with the 'mirror' segment type is composed of mirror images
1331 # (copies) and a mirror log. A disk log ensures that a mirror LV does
1332 # not need to be re-synced (all copies made the same) every time a
1333 # machine reboots or crashes. If a device in the LV fails, this policy
1334 # determines the steps perfomed by dmeventd automatically, and the steps
1335 # performed by the manual command lvconvert --repair --use-policies.
1336 # Automatic handling requires dmeventd to be monitoring the LV.
1340 # Simply remove the faulty device and run without it. If the log
1341 # device fails, the mirror would convert to using an in-memory log.
1342 # This means the mirror will not remember its sync status across
1343 # crashes/reboots and the entire mirror will be re-synced. If a
1344 # mirror image fails, the mirror will convert to a non-mirrored
1345 # device if there is only one remaining good copy.
1347 # Remove the faulty device and try to allocate space on a new
1348 # device to be a replacement for the failed device. Using this
1349 # policy for the log is fast and maintains the ability to remember
1350 # sync state through crashes/reboots. Using this policy for a
1351 # mirror device is slow, as it requires the mirror to resynchronize
1352 # the devices, but it will preserve the mirror characteristic of
1353 # the device. This policy acts like 'remove' if no suitable device
1354 # and space can be allocated for the replacement.
1356 # Not yet implemented. Useful to place the log device temporarily
1357 # on the same physical volume as one of the mirror images. This
1358 # policy is not recommended for mirror devices since it would break
1359 # the redundant nature of the mirror. This policy acts like
1360 # 'remove' if no suitable device and space can be allocated for the
1363 mirror_image_fault_policy = "remove"
1365 # Configuration option activation/mirror_log_fault_policy.
1366 # Defines how a device failure in a 'mirror' log LV is handled.
1367 # The mirror_image_fault_policy description for mirrored LVs also
1368 # applies to mirrored log LVs.
1369 mirror_log_fault_policy = "allocate"
1371 # Configuration option activation/snapshot_autoextend_threshold.
1372 # Auto-extend a snapshot when its usage exceeds this percent.
1373 # Setting this to 100 disables automatic extension.
1374 # The minimum value is 50 (a smaller value is treated as 50.)
1375 # Also see snapshot_autoextend_percent.
1376 # Automatic extension requires dmeventd to be monitoring the LV.
1379 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1380 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1381 # 840M, it is extended to 1.44G:
1382 # snapshot_autoextend_threshold = 70
1384 snapshot_autoextend_threshold = 100
1386 # Configuration option activation/snapshot_autoextend_percent.
1387 # Auto-extending a snapshot adds this percent extra space.
1388 # The amount of additional space added to a snapshot is this
1389 # percent of its current size.
1392 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1393 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1394 # 840M, it is extended to 1.44G:
1395 # snapshot_autoextend_percent = 20
1397 snapshot_autoextend_percent = 20
1399 # Configuration option activation/thin_pool_autoextend_threshold.
1400 # Auto-extend a thin pool when its usage exceeds this percent.
1401 # Setting this to 100 disables automatic extension.
1402 # The minimum value is 50 (a smaller value is treated as 50.)
1403 # Also see thin_pool_autoextend_percent.
1404 # Automatic extension requires dmeventd to be monitoring the LV.
1407 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1408 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1409 # 840M, it is extended to 1.44G:
1410 # thin_pool_autoextend_threshold = 70
1412 thin_pool_autoextend_threshold = 100
1414 # Configuration option activation/thin_pool_autoextend_percent.
1415 # Auto-extending a thin pool adds this percent extra space.
1416 # The amount of additional space added to a thin pool is this
1417 # percent of its current size.
1420 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1421 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1422 # 840M, it is extended to 1.44G:
1423 # thin_pool_autoextend_percent = 20
1425 thin_pool_autoextend_percent = 20
1427 # Configuration option activation/mlock_filter.
1428 # Do not mlock these memory areas.
1429 # While activating devices, I/O to devices being (re)configured is
1430 # suspended. As a precaution against deadlocks, LVM pins memory it is
1431 # using so it is not paged out, and will not require I/O to reread.
1432 # Groups of pages that are known not to be accessed during activation
1433 # do not need to be pinned into memory. Each string listed in this
1434 # setting is compared against each line in /proc/self/maps, and the
1435 # pages corresponding to lines that match are not pinned. On some
1436 # systems, locale-archive was found to make up over 80% of the memory
1437 # used by the process.
1440 # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
1442 # This configuration option is advanced.
1443 # This configuration option does not have a default value defined.
1445 # Configuration option activation/use_mlockall.
1446 # Use the old behavior of mlockall to pin all memory.
1447 # Prior to version 2.02.62, LVM used mlockall() to pin the whole
1448 # process's memory while activating devices.
1451 # Configuration option activation/monitoring.
1452 # Monitor LVs that are activated.
1453 # The --ignoremonitoring option overrides this setting.
1454 # When enabled, LVM will ask dmeventd to monitor activated LVs.
1457 # Configuration option activation/polling_interval.
1458 # Check pvmove or lvconvert progress at this interval (seconds).
1459 # When pvmove or lvconvert must wait for the kernel to finish
1460 # synchronising or merging data, they check and report progress at
1461 # intervals of this number of seconds. If this is set to 0 and there
1462 # is only one thing to wait for, there are no progress reports, but
1463 # the process is awoken immediately once the operation is complete.
1464 polling_interval = 15
1466 # Configuration option activation/auto_set_activation_skip.
1467 # Set the activation skip flag on new thin snapshot LVs.
1468 # The --setactivationskip option overrides this setting.
1469 # An LV can have a persistent 'activation skip' flag. The flag causes
1470 # the LV to be skipped during normal activation. The lvchange/vgchange
1471 # -K option is required to activate LVs that have the activation skip
1472 # flag set. When this setting is enabled, the activation skip flag is
1473 # set on new thin snapshot LVs.
1474 # This configuration option has an automatic default value.
1475 # auto_set_activation_skip = 1
1477 # Configuration option activation/activation_mode.
1478 # How LVs with missing devices are activated.
1479 # The --activationmode option overrides this setting.
1483 # Only allow activation of an LV if all of the Physical Volumes it
1484 # uses are present. Other PVs in the Volume Group may be missing.
1486 # Like complete, but additionally RAID LVs of segment type raid1,
1487 # raid4, raid5, radid6 and raid10 will be activated if there is no
1488 # data loss, i.e. they have sufficient redundancy to present the
1489 # entire addressable range of the Logical Volume.
1491 # Allows the activation of any LV even if a missing or failed PV
1492 # could cause data loss with a portion of the LV inaccessible.
1493 # This setting should not normally be used, but may sometimes
1494 # assist with data recovery.
1496 activation_mode = "degraded"
1498 # Configuration option activation/lock_start_list.
1499 # Locking is started only for VGs selected by this list.
1500 # The rules are the same as those for volume_list.
1501 # This configuration option does not have a default value defined.
1503 # Configuration option activation/auto_lock_start_list.
1504 # Locking is auto-started only for VGs selected by this list.
1505 # The rules are the same as those for auto_activation_volume_list.
1506 # This configuration option does not have a default value defined.
1509 # Configuration section metadata.
1510 # This configuration section has an automatic default value.
1513 # Configuration option metadata/check_pv_device_sizes.
1514 # Check device sizes are not smaller than corresponding PV sizes.
1515 # If device size is less than corresponding PV size found in metadata,
1516 # there is always a risk of data loss. If this option is set, then LVM
1517 # issues a warning message each time it finds that the device size is
1518 # less than corresponding PV size. You should not disable this unless
1519 # you are absolutely sure about what you are doing!
1520 # This configuration option is advanced.
1521 # This configuration option has an automatic default value.
1522 # check_pv_device_sizes = 1
1524 # Configuration option metadata/record_lvs_history.
1525 # When enabled, LVM keeps history records about removed LVs in
1526 # metadata. The information that is recorded in metadata for
1527 # historical LVs is reduced when compared to original
1528 # information kept in metadata for live LVs. Currently, this
1529 # feature is supported for thin and thin snapshot LVs only.
1530 # This configuration option has an automatic default value.
1531 # record_lvs_history = 0
1533 # Configuration option metadata/lvs_history_retention_time.
1534 # Retention time in seconds after which a record about individual
1535 # historical logical volume is automatically destroyed.
1536 # A value of 0 disables this feature.
1537 # This configuration option has an automatic default value.
1538 # lvs_history_retention_time = 0
1540 # Configuration option metadata/pvmetadatacopies.
1541 # Number of copies of metadata to store on each PV.
1542 # The --pvmetadatacopies option overrides this setting.
1546 # Two copies of the VG metadata are stored on the PV, one at the
1547 # front of the PV, and one at the end.
1549 # One copy of VG metadata is stored at the front of the PV.
1551 # No copies of VG metadata are stored on the PV. This may be
1552 # useful for VGs containing large numbers of PVs.
1554 # This configuration option is advanced.
1555 # This configuration option has an automatic default value.
1556 # pvmetadatacopies = 1
1558 # Configuration option metadata/vgmetadatacopies.
1559 # Number of copies of metadata to maintain for each VG.
1560 # The --vgmetadatacopies option overrides this setting.
1561 # If set to a non-zero value, LVM automatically chooses which of the
1562 # available metadata areas to use to achieve the requested number of
1563 # copies of the VG metadata. If you set a value larger than the the
1564 # total number of metadata areas available, then metadata is stored in
1565 # them all. The value 0 (unmanaged) disables this automatic management
1566 # and allows you to control which metadata areas are used at the
1567 # individual PV level using pvchange --metadataignore y|n.
1568 # This configuration option has an automatic default value.
1569 # vgmetadatacopies = 0
1571 # Configuration option metadata/pvmetadatasize.
1572 # Approximate number of sectors to use for each metadata copy.
1573 # VGs with large numbers of PVs or LVs, or VGs containing complex LV
1574 # structures, may need additional space for VG metadata. The metadata
1575 # areas are treated as circular buffers, so unused space becomes filled
1576 # with an archive of the most recent previous versions of the metadata.
1577 # This configuration option has an automatic default value.
1578 # pvmetadatasize = 255
1580 # Configuration option metadata/pvmetadataignore.
1581 # Ignore metadata areas on a new PV.
1582 # The --metadataignore option overrides this setting.
1583 # If metadata areas on a PV are ignored, LVM will not store metadata
1585 # This configuration option is advanced.
1586 # This configuration option has an automatic default value.
1587 # pvmetadataignore = 0
1589 # Configuration option metadata/stripesize.
1590 # This configuration option is advanced.
1591 # This configuration option has an automatic default value.
1594 # Configuration option metadata/dirs.
1595 # Directories holding live copies of text format metadata.
1596 # These directories must not be on logical volumes!
1597 # It's possible to use LVM with a couple of directories here,
1598 # preferably on different (non-LV) filesystems, and with no other
1599 # on-disk metadata (pvmetadatacopies = 0). Or this can be in addition
1600 # to on-disk metadata areas. The feature was originally added to
1601 # simplify testing and is not supported under low memory situations -
1602 # the machine could lock up. Never edit any files in these directories
1603 # by hand unless you are absolutely sure you know what you are doing!
1604 # Use the supplied toolset to make changes (e.g. vgcfgrestore).
1607 # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
1609 # This configuration option is advanced.
1610 # This configuration option does not have a default value defined.
1613 # Configuration section report.
1614 # LVM report command output formatting.
1615 # This configuration section has an automatic default value.
1618 # Configuration option report/output_format.
1619 # Format of LVM command's report output.
1620 # If there is more than one report per command, then the format
1621 # is applied for all reports. You can also change output format
1622 # directly on command line using --reportformat option which
1623 # has precedence over log/output_format setting.
1626 # Original format with columns and rows. If there is more than
1627 # one report per command, each report is prefixed with report's
1628 # name for identification.
1631 # This configuration option has an automatic default value.
1632 # output_format = "basic"
1634 # Configuration option report/compact_output.
1635 # Do not print empty values for all report fields.
1636 # If enabled, all fields that don't have a value set for any of the
1637 # rows reported are skipped and not printed. Compact output is
1638 # applicable only if report/buffered is enabled. If you need to
1639 # compact only specified fields, use compact_output=0 and define
1640 # report/compact_output_cols configuration setting instead.
1641 # This configuration option has an automatic default value.
1642 # compact_output = 0
1644 # Configuration option report/compact_output_cols.
1645 # Do not print empty values for specified report fields.
1646 # If defined, specified fields that don't have a value set for any
1647 # of the rows reported are skipped and not printed. Compact output
1648 # is applicable only if report/buffered is enabled. If you need to
1649 # compact all fields, use compact_output=1 instead in which case
1650 # the compact_output_cols setting is then ignored.
1651 # This configuration option has an automatic default value.
1652 # compact_output_cols = ""
1654 # Configuration option report/aligned.
1655 # Align columns in report output.
1656 # This configuration option has an automatic default value.
1659 # Configuration option report/buffered.
1660 # Buffer report output.
1661 # When buffered reporting is used, the report's content is appended
1662 # incrementally to include each object being reported until the report
1663 # is flushed to output which normally happens at the end of command
1664 # execution. Otherwise, if buffering is not used, each object is
1665 # reported as soon as its processing is finished.
1666 # This configuration option has an automatic default value.
1669 # Configuration option report/headings.
1670 # Show headings for columns on report.
1671 # This configuration option has an automatic default value.
1674 # Configuration option report/separator.
1675 # A separator to use on report after each field.
1676 # This configuration option has an automatic default value.
1679 # Configuration option report/list_item_separator.
1680 # A separator to use for list items when reported.
1681 # This configuration option has an automatic default value.
1682 # list_item_separator = ","
1684 # Configuration option report/prefixes.
1685 # Use a field name prefix for each field reported.
1686 # This configuration option has an automatic default value.
1689 # Configuration option report/quoted.
1690 # Quote field values when using field name prefixes.
1691 # This configuration option has an automatic default value.
1694 # Configuration option report/columns_as_rows.
1695 # Output each column as a row.
1696 # If set, this also implies report/prefixes=1.
1697 # This configuration option has an automatic default value.
1698 # columns_as_rows = 0
1700 # Configuration option report/binary_values_as_numeric.
1701 # Use binary values 0 or 1 instead of descriptive literal values.
1702 # For columns that have exactly two valid values to report
1703 # (not counting the 'unknown' value which denotes that the
1704 # value could not be determined).
1705 # This configuration option has an automatic default value.
1706 # binary_values_as_numeric = 0
1708 # Configuration option report/time_format.
1709 # Set time format for fields reporting time values.
1710 # Format specification is a string which may contain special character
1711 # sequences and ordinary character sequences. Ordinary character
1712 # sequences are copied verbatim. Each special character sequence is
1713 # introduced by the '%' character and such sequence is then
1714 # substituted with a value as described below.
1718 # The abbreviated name of the day of the week according to the
1721 # The full name of the day of the week according to the current
1724 # The abbreviated month name according to the current locale.
1726 # The full month name according to the current locale.
1728 # The preferred date and time representation for the current
1731 # The century number (year/100) as a 2-digit integer. (alt E)
1733 # The day of the month as a decimal number (range 01 to 31).
1736 # Equivalent to %m/%d/%y. (For Americans only. Americans should
1737 # note that in other countries%d/%m/%y is rather common. This
1738 # means that in international context this format is ambiguous and
1739 # should not be used.
1741 # Like %d, the day of the month as a decimal number, but a leading
1742 # zero is replaced by a space. (alt O)
1744 # Modifier: use alternative local-dependent representation if
1747 # Equivalent to %Y-%m-%d (the ISO 8601 date format).
1749 # The ISO 8601 week-based year with century as adecimal number.
1750 # The 4-digit year corresponding to the ISO week number (see %V).
1751 # This has the same format and value as %Y, except that if the
1752 # ISO week number belongs to the previous or next year, that year
1755 # Like %G, but without century, that is, with a 2-digit year
1760 # The hour as a decimal number using a 24-hour clock
1761 # (range 00 to 23). (alt O)
1763 # The hour as a decimal number using a 12-hour clock
1764 # (range 01 to 12). (alt O)
1766 # The day of the year as a decimal number (range 001 to 366).
1768 # The hour (24-hour clock) as a decimal number (range 0 to 23);
1769 # single digits are preceded by a blank. (See also %H.)
1771 # The hour (12-hour clock) as a decimal number (range 1 to 12);
1772 # single digits are preceded by a blank. (See also %I.)
1774 # The month as a decimal number (range 01 to 12). (alt O)
1776 # The minute as a decimal number (range 00 to 59). (alt O)
1778 # Modifier: use alternative numeric symbols.
1780 # Either "AM" or "PM" according to the given time value,
1781 # or the corresponding strings for the current locale. Noon is
1782 # treated as "PM" and midnight as "AM".
1784 # Like %p but in lowercase: "am" or "pm" or a corresponding
1785 # string for the current locale.
1787 # The time in a.m. or p.m. notation. In the POSIX locale this is
1788 # equivalent to %I:%M:%S %p.
1790 # The time in 24-hour notation (%H:%M). For a version including
1791 # the seconds, see %T below.
1793 # The number of seconds since the Epoch,
1794 # 1970-01-01 00:00:00 +0000 (UTC)
1796 # The second as a decimal number (range 00 to 60). (The range is
1797 # up to 60 to allow for occasional leap seconds.) (alt O)
1801 # The time in 24-hour notation (%H:%M:%S).
1803 # The day of the week as a decimal, range 1 to 7, Monday being 1.
1804 # See also %w. (alt O)
1806 # The week number of the current year as a decimal number,
1807 # range 00 to 53, starting with the first Sunday as the first
1808 # day of week 01. See also %V and %W. (alt O)
1810 # The ISO 8601 week number of the current year as a decimal number,
1811 # range 01 to 53, where week 1 is the first week that has at least
1812 # 4 days in the new year. See also %U and %W. (alt O)
1814 # The day of the week as a decimal, range 0 to 6, Sunday being 0.
1815 # See also %u. (alt O)
1817 # The week number of the current year as a decimal number,
1818 # range 00 to 53, starting with the first Monday as the first day
1819 # of week 01. (alt O)
1821 # The preferred date representation for the current locale without
1824 # The preferred time representation for the current locale without
1827 # The year as a decimal number without a century (range 00 to 99).
1830 # The year as a decimal number including the century. (alt E)
1832 # The +hhmm or -hhmm numeric timezone (that is, the hour and minute
1835 # The timezone name or abbreviation.
1837 # A literal '%' character.
1839 # This configuration option has an automatic default value.
1840 # time_format = "%Y-%m-%d %T %z"
1842 # Configuration option report/devtypes_sort.
1843 # List of columns to sort by when reporting 'lvm devtypes' command.
1844 # See 'lvm devtypes -o help' for the list of possible fields.
1845 # This configuration option has an automatic default value.
1846 # devtypes_sort = "devtype_name"
1848 # Configuration option report/devtypes_cols.
1849 # List of columns to report for 'lvm devtypes' command.
1850 # See 'lvm devtypes -o help' for the list of possible fields.
1851 # This configuration option has an automatic default value.
1852 # devtypes_cols = "devtype_name,devtype_max_partitions,devtype_description"
1854 # Configuration option report/devtypes_cols_verbose.
1855 # List of columns to report for 'lvm devtypes' command in verbose mode.
1856 # See 'lvm devtypes -o help' for the list of possible fields.
1857 # This configuration option has an automatic default value.
1858 # devtypes_cols_verbose = "devtype_name,devtype_max_partitions,devtype_description"
1860 # Configuration option report/lvs_sort.
1861 # List of columns to sort by when reporting 'lvs' command.
1862 # See 'lvs -o help' for the list of possible fields.
1863 # This configuration option has an automatic default value.
1864 # lvs_sort = "vg_name,lv_name"
1866 # Configuration option report/lvs_cols.
1867 # List of columns to report for 'lvs' command.
1868 # See 'lvs -o help' for the list of possible fields.
1869 # This configuration option has an automatic default value.
1870 # 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"
1872 # Configuration option report/lvs_cols_verbose.
1873 # List of columns to report for 'lvs' command in verbose mode.
1874 # See 'lvs -o help' for the list of possible fields.
1875 # This configuration option has an automatic default value.
1876 # 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"
1878 # Configuration option report/vgs_sort.
1879 # List of columns to sort by when reporting 'vgs' command.
1880 # See 'vgs -o help' for the list of possible fields.
1881 # This configuration option has an automatic default value.
1882 # vgs_sort = "vg_name"
1884 # Configuration option report/vgs_cols.
1885 # List of columns to report for 'vgs' command.
1886 # See 'vgs -o help' for the list of possible fields.
1887 # This configuration option has an automatic default value.
1888 # vgs_cols = "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
1890 # Configuration option report/vgs_cols_verbose.
1891 # List of columns to report for 'vgs' command in verbose mode.
1892 # See 'vgs -o help' for the list of possible fields.
1893 # This configuration option has an automatic default value.
1894 # vgs_cols_verbose = "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
1896 # Configuration option report/pvs_sort.
1897 # List of columns to sort by when reporting 'pvs' command.
1898 # See 'pvs -o help' for the list of possible fields.
1899 # This configuration option has an automatic default value.
1900 # pvs_sort = "pv_name"
1902 # Configuration option report/pvs_cols.
1903 # List of columns to report for 'pvs' command.
1904 # See 'pvs -o help' for the list of possible fields.
1905 # This configuration option has an automatic default value.
1906 # pvs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
1908 # Configuration option report/pvs_cols_verbose.
1909 # List of columns to report for 'pvs' command in verbose mode.
1910 # See 'pvs -o help' for the list of possible fields.
1911 # This configuration option has an automatic default value.
1912 # pvs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
1914 # Configuration option report/segs_sort.
1915 # List of columns to sort by when reporting 'lvs --segments' command.
1916 # See 'lvs --segments -o help' for the list of possible fields.
1917 # This configuration option has an automatic default value.
1918 # segs_sort = "vg_name,lv_name,seg_start"
1920 # Configuration option report/segs_cols.
1921 # List of columns to report for 'lvs --segments' command.
1922 # See 'lvs --segments -o help' for the list of possible fields.
1923 # This configuration option has an automatic default value.
1924 # segs_cols = "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
1926 # Configuration option report/segs_cols_verbose.
1927 # List of columns to report for 'lvs --segments' command in verbose mode.
1928 # See 'lvs --segments -o help' for the list of possible fields.
1929 # This configuration option has an automatic default value.
1930 # segs_cols_verbose = "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
1932 # Configuration option report/pvsegs_sort.
1933 # List of columns to sort by when reporting 'pvs --segments' command.
1934 # See 'pvs --segments -o help' for the list of possible fields.
1935 # This configuration option has an automatic default value.
1936 # pvsegs_sort = "pv_name,pvseg_start"
1938 # Configuration option report/pvsegs_cols.
1939 # List of columns to sort by when reporting 'pvs --segments' command.
1940 # See 'pvs --segments -o help' for the list of possible fields.
1941 # This configuration option has an automatic default value.
1942 # pvsegs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
1944 # Configuration option report/pvsegs_cols_verbose.
1945 # List of columns to sort by when reporting 'pvs --segments' command in verbose mode.
1946 # See 'pvs --segments -o help' for the list of possible fields.
1947 # This configuration option has an automatic default value.
1948 # 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"
1950 # Configuration option report/vgs_cols_full.
1951 # List of columns to report for lvm fullreport's 'vgs' subreport.
1952 # See 'vgs -o help' for the list of possible fields.
1953 # This configuration option has an automatic default value.
1954 # vgs_cols_full = "vg_all"
1956 # Configuration option report/pvs_cols_full.
1957 # List of columns to report for lvm fullreport's 'vgs' subreport.
1958 # See 'pvs -o help' for the list of possible fields.
1959 # This configuration option has an automatic default value.
1960 # pvs_cols_full = "pv_all"
1962 # Configuration option report/lvs_cols_full.
1963 # List of columns to report for lvm fullreport's 'lvs' subreport.
1964 # See 'lvs -o help' for the list of possible fields.
1965 # This configuration option has an automatic default value.
1966 # lvs_cols_full = "lv_all"
1968 # Configuration option report/pvsegs_cols_full.
1969 # List of columns to report for lvm fullreport's 'pvseg' subreport.
1970 # See 'pvs --segments -o help' for the list of possible fields.
1971 # This configuration option has an automatic default value.
1972 # pvsegs_cols_full = "pvseg_all,pv_uuid,lv_uuid"
1974 # Configuration option report/segs_cols_full.
1975 # List of columns to report for lvm fullreport's 'seg' subreport.
1976 # See 'lvs --segments -o help' for the list of possible fields.
1977 # This configuration option has an automatic default value.
1978 # segs_cols_full = "seg_all,lv_uuid"
1980 # Configuration option report/vgs_sort_full.
1981 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
1982 # See 'vgs -o help' for the list of possible fields.
1983 # This configuration option has an automatic default value.
1984 # vgs_sort_full = "vg_name"
1986 # Configuration option report/pvs_sort_full.
1987 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
1988 # See 'pvs -o help' for the list of possible fields.
1989 # This configuration option has an automatic default value.
1990 # pvs_sort_full = "pv_name"
1992 # Configuration option report/lvs_sort_full.
1993 # List of columns to sort by when reporting lvm fullreport's 'lvs' subreport.
1994 # See 'lvs -o help' for the list of possible fields.
1995 # This configuration option has an automatic default value.
1996 # lvs_sort_full = "vg_name,lv_name"
1998 # Configuration option report/pvsegs_sort_full.
1999 # List of columns to sort by when reporting for lvm fullreport's 'pvseg' subreport.
2000 # See 'pvs --segments -o help' for the list of possible fields.
2001 # This configuration option has an automatic default value.
2002 # pvsegs_sort_full = "pv_uuid,pvseg_start"
2004 # Configuration option report/segs_sort_full.
2005 # List of columns to sort by when reporting lvm fullreport's 'seg' subreport.
2006 # See 'lvs --segments -o help' for the list of possible fields.
2007 # This configuration option has an automatic default value.
2008 # segs_sort_full = "lv_uuid,seg_start"
2010 # Configuration option report/mark_hidden_devices.
2011 # Use brackets [] to mark hidden devices.
2012 # This configuration option has an automatic default value.
2013 # mark_hidden_devices = 1
2015 # Configuration option report/two_word_unknown_device.
2016 # Use the two words 'unknown device' in place of '[unknown]'.
2017 # This is displayed when the device for a PV is not known.
2018 # This configuration option has an automatic default value.
2019 # two_word_unknown_device = 0
2022 # Configuration section dmeventd.
2023 # Settings for the LVM event daemon.
2026 # Configuration option dmeventd/mirror_library.
2027 # The library dmeventd uses when monitoring a mirror device.
2028 # libdevmapper-event-lvm2mirror.so attempts to recover from
2029 # failures. It removes failed devices from a volume group and
2030 # reconfigures a mirror as necessary. If no mirror library is
2031 # provided, mirrors are not monitored through dmeventd.
2032 mirror_library = "libdevmapper-event-lvm2mirror.so"
2034 # Configuration option dmeventd/raid_library.
2035 # This configuration option has an automatic default value.
2036 # raid_library = "libdevmapper-event-lvm2raid.so"
2038 # Configuration option dmeventd/snapshot_library.
2039 # The library dmeventd uses when monitoring a snapshot device.
2040 # libdevmapper-event-lvm2snapshot.so monitors the filling of snapshots
2041 # and emits a warning through syslog when the usage exceeds 80%. The
2042 # warning is repeated when 85%, 90% and 95% of the snapshot is filled.
2043 snapshot_library = "libdevmapper-event-lvm2snapshot.so"
2045 # Configuration option dmeventd/thin_library.
2046 # The library dmeventd uses when monitoring a thin device.
2047 # libdevmapper-event-lvm2thin.so monitors the filling of a pool
2048 # and emits a warning through syslog when the usage exceeds 80%. The
2049 # warning is repeated when 85%, 90% and 95% of the pool is filled.
2050 thin_library = "libdevmapper-event-lvm2thin.so"
2052 # Configuration option dmeventd/executable.
2053 # The full path to the dmeventd binary.
2054 # This configuration option has an automatic default value.
2055 # executable = "/sbin/dmeventd"
2058 # Configuration section tags.
2059 # Host tag settings.
2060 # This configuration section has an automatic default value.
2063 # Configuration option tags/hosttags.
2064 # Create a host tag using the machine name.
2065 # The machine name is nodename returned by uname(2).
2066 # This configuration option has an automatic default value.
2069 # Configuration section tags/<tag>.
2070 # Replace this subsection name with a custom tag name.
2071 # Multiple subsections like this can be created. The '@' prefix for
2072 # tags is optional. This subsection can contain host_list, which is a
2073 # list of machine names. If the name of the local machine is found in
2074 # host_list, then the name of this subsection is used as a tag and is
2075 # applied to the local machine as a 'host tag'. If this subsection is
2076 # empty (has no host_list), then the subsection name is always applied
2080 # The host tag foo is given to all hosts, and the host tag
2081 # bar is given to the hosts named machine1 and machine2.
2082 # tags { foo { } bar { host_list = [ "machine1", "machine2" ] } }
2084 # This configuration section has variable name.
2085 # This configuration section has an automatic default value.
2088 # Configuration option tags/<tag>/host_list.
2089 # A list of machine names.
2090 # These machine names are compared to the nodename returned
2091 # by uname(2). If the local machine name matches an entry in
2092 # this list, the name of the subsection is applied to the
2093 # machine as a 'host tag'.
2094 # This configuration option does not have a default value defined.