1 # This is an example configuration file for the LVM2 system.
2 # It contains the default settings that would be used if there was no
3 # /etc/lvm/lvm.conf file.
5 # Refer to 'man lvm.conf' for further information including the file layout.
7 # Refer to 'man lvm.conf' for information about how settings configured in
8 # this file are combined with built-in values and command line options to
9 # arrive at the final values used by LVM.
11 # Refer to 'man lvmconfig' for information about displaying the built-in
12 # and configured values used by LVM.
14 # If a default value is set in this file (not commented out), then a
15 # new version of LVM using this file will continue using that value,
16 # even if the new version of LVM changes the built-in default value.
18 # To put this file in a different directory and override /etc/lvm set
19 # the environment variable LVM_SYSTEM_DIR before running the tools.
21 # N.B. Take care that each setting only appears once if uncommenting
22 # example settings in this file.
25 # Configuration section config.
26 # How LVM configuration settings are handled.
29 # Configuration option config/checks.
30 # If enabled, any LVM configuration mismatch is reported.
31 # This implies checking that the configuration key is understood by
32 # LVM and that the value of the key is the proper type. If disabled,
33 # any configuration mismatch is ignored and the default value is used
34 # without any warning (a message about the configuration key not being
35 # found is issued in verbose mode only).
38 # Configuration option config/abort_on_errors.
39 # Abort the LVM process if a configuration mismatch is found.
42 # Configuration option config/profile_dir.
43 # Directory where LVM looks for configuration profiles.
44 profile_dir = "/etc/lvm/profile"
47 # Configuration section devices.
48 # How LVM uses block devices.
51 # Configuration option devices/dir.
52 # Directory in which to create volume group device nodes.
53 # Commands also accept this as a prefix on volume group names.
54 # This configuration option is advanced.
57 # Configuration option devices/scan.
58 # Directories containing device nodes to use with LVM.
59 # This configuration option is advanced.
62 # Configuration option devices/obtain_device_list_from_udev.
63 # Obtain the list of available devices from udev.
64 # This avoids opening or using any inapplicable non-block devices or
65 # subdirectories found in the udev directory. Any device node or
66 # symlink not managed by udev in the udev directory is ignored. This
67 # setting applies only to the udev-managed device directory; other
68 # directories will be scanned fully. LVM needs to be compiled with
69 # udev support for this setting to apply.
70 obtain_device_list_from_udev = 1
72 # Configuration option devices/external_device_info_source.
73 # Select an external device information source.
74 # Some information may already be available in the system and LVM can
75 # use this information to determine the exact type or use of devices it
76 # processes. Using an existing external device information source can
77 # speed up device processing as LVM does not need to run its own native
78 # routines to acquire this information. For example, this information
79 # is used to drive LVM filtering like MD component detection, multipath
80 # component detection, partition detection and others.
84 # No external device information source is used.
86 # Reuse existing udev database records. Applicable only if LVM is
87 # compiled with udev support.
89 external_device_info_source = "none"
91 # Configuration option devices/preferred_names.
92 # Select which path name to display for a block device.
93 # If multiple path names exist for a block device, and LVM needs to
94 # display a name for the device, the path names are matched against
95 # each item in this list of regular expressions. The first match is
96 # used. Try to avoid using undescriptive /dev/dm-N names, if present.
97 # If no preferred name matches, or if preferred_names are not defined,
98 # the following built-in preferences are applied in order until one
99 # produces a preferred name:
100 # Prefer names with path prefixes in the order of:
101 # /dev/mapper, /dev/disk, /dev/dm-*, /dev/block.
102 # Prefer the name with the least number of slashes.
103 # Prefer a name that is a symlink.
104 # Prefer the path with least value in lexicographical order.
107 # preferred_names = [ "^/dev/mpath/", "^/dev/mapper/mpath", "^/dev/[hs]d" ]
109 # This configuration option does not have a default value defined.
110 preferred_names = [ ]
112 # Configuration option devices/filter.
113 # Limit the block devices that are used by LVM commands.
114 # This is a list of regular expressions used to accept or reject block
115 # device path names. Each regex is delimited by a vertical bar '|'
116 # (or any character) and is preceded by 'a' to accept the path, or
117 # by 'r' to reject the path. The first regex in the list to match the
118 # path is used, producing the 'a' or 'r' result for the device.
119 # When multiple path names exist for a block device, if any path name
120 # matches an 'a' pattern before an 'r' pattern, then the device is
121 # accepted. If all the path names match an 'r' pattern first, then the
122 # device is rejected. Unmatching path names do not affect the accept
123 # or reject decision. If no path names for a device match a pattern,
124 # then the device is accepted. Be careful mixing 'a' and 'r' patterns,
125 # as the combination might produce unexpected results (test changes.)
126 # Run vgscan after changing the filter to regenerate the cache.
127 # See the use_lvmetad comment for a special case regarding filters.
130 # Accept every block device:
131 # filter = [ "a|.*/|" ]
132 # Reject the cdrom drive:
133 # filter = [ "r|/dev/cdrom|" ]
134 # Work with just loopback devices, e.g. for testing:
135 # filter = [ "a|loop|", "r|.*|" ]
136 # Accept all loop devices and ide drives except hdc:
137 # filter = [ "a|loop|", "r|/dev/hdc|", "a|/dev/ide|", "r|.*|" ]
138 # Use anchors to be very specific:
139 # filter = [ "a|^/dev/hda8$|", "r|.*/|" ]
141 # This configuration option has an automatic default value.
142 # filter = [ "a|.*/|" ]
143 filter = [ "a|^/dev/md[0-9]*$|", "r/.*/" ]
145 # Configuration option devices/global_filter.
146 # Limit the block devices that are used by LVM system components.
147 # Because devices/filter may be overridden from the command line, it is
148 # not suitable for system-wide device filtering, e.g. udev and lvmetad.
149 # Use global_filter to hide devices from these LVM system components.
150 # The syntax is the same as devices/filter. Devices rejected by
151 # global_filter are not opened by LVM.
152 # This configuration option has an automatic default value.
153 # global_filter = [ "a|.*/|" ]
154 global_filter = [ "a|^/dev/md[0-9]*$|", "r/.*/" ]
156 # Configuration option devices/cache_dir.
157 # Directory in which to store the device cache file.
158 # The results of filtering are cached on disk to avoid rescanning dud
159 # devices (which can take a very long time). By default this cache is
160 # stored in a file named .cache. It is safe to delete this file; the
161 # tools regenerate it. If obtain_device_list_from_udev is enabled, the
162 # list of devices is obtained from udev and any existing .cache file
164 cache_dir = "/run/lvm"
166 # Configuration option devices/cache_file_prefix.
167 # A prefix used before the .cache file name. See devices/cache_dir.
168 cache_file_prefix = ""
170 # Configuration option devices/write_cache_state.
171 # Enable/disable writing the cache file. See devices/cache_dir.
172 write_cache_state = 1
174 # Configuration option devices/types.
175 # List of additional acceptable block device types.
176 # These are of device type names from /proc/devices, followed by the
177 # maximum number of partitions.
180 # types = [ "fd", 16 ]
182 # This configuration option is advanced.
183 # This configuration option does not have a default value defined.
185 # Configuration option devices/sysfs_scan.
186 # Restrict device scanning to block devices appearing in sysfs.
187 # This is a quick way of filtering out block devices that are not
188 # present on the system. sysfs must be part of the kernel and mounted.)
191 # Configuration option devices/multipath_component_detection.
192 # Ignore devices that are components of DM multipath devices.
193 multipath_component_detection = 1
195 # Configuration option devices/md_component_detection.
196 # Ignore devices that are components of software RAID (md) devices.
197 md_component_detection = 1
199 # Configuration option devices/fw_raid_component_detection.
200 # Ignore devices that are components of firmware RAID devices.
201 # LVM must use an external_device_info_source other than none for this
202 # detection to execute.
203 fw_raid_component_detection = 0
205 # Configuration option devices/md_chunk_alignment.
206 # Align PV data blocks with md device's stripe-width.
207 # This applies if a PV is placed directly on an md device.
208 md_chunk_alignment = 1
210 # Configuration option devices/default_data_alignment.
211 # Default alignment of the start of a PV data area in MB.
212 # If set to 0, a value of 64KiB will be used.
213 # Set to 1 for 1MiB, 2 for 2MiB, etc.
214 # This configuration option has an automatic default value.
215 # default_data_alignment = 1
217 # Configuration option devices/data_alignment_detection.
218 # Detect PV data alignment based on sysfs device information.
219 # The start of a PV data area will be a multiple of minimum_io_size or
220 # optimal_io_size exposed in sysfs. minimum_io_size is the smallest
221 # request the device can perform without incurring a read-modify-write
222 # penalty, e.g. MD chunk size. optimal_io_size is the device's
223 # preferred unit of receiving I/O, e.g. MD stripe width.
224 # minimum_io_size is used if optimal_io_size is undefined (0).
225 # If md_chunk_alignment is enabled, that detects the optimal_io_size.
226 # This setting takes precedence over md_chunk_alignment.
227 data_alignment_detection = 1
229 # Configuration option devices/data_alignment.
230 # Alignment of the start of a PV data area in KiB.
231 # If a PV is placed directly on an md device and md_chunk_alignment or
232 # data_alignment_detection are enabled, then this setting is ignored.
233 # Otherwise, md_chunk_alignment and data_alignment_detection are
234 # disabled if this is set. Set to 0 to use the default alignment or the
235 # page size, if larger.
238 # Configuration option devices/data_alignment_offset_detection.
239 # Detect PV data alignment offset based on sysfs device information.
240 # The start of a PV aligned data area will be shifted by the
241 # alignment_offset exposed in sysfs. This offset is often 0, but may
242 # be non-zero. Certain 4KiB sector drives that compensate for windows
243 # partitioning will have an alignment_offset of 3584 bytes (sector 7
244 # is the lowest aligned logical block, the 4KiB sectors start at
245 # LBA -1, and consequently sector 63 is aligned on a 4KiB boundary).
246 # pvcreate --dataalignmentoffset will skip this detection.
247 data_alignment_offset_detection = 1
249 # Configuration option devices/ignore_suspended_devices.
250 # Ignore DM devices that have I/O suspended while scanning devices.
251 # Otherwise, LVM waits for a suspended device to become accessible.
252 # This should only be needed in recovery situations.
253 ignore_suspended_devices = 0
255 # Configuration option devices/ignore_lvm_mirrors.
256 # Do not scan 'mirror' LVs to avoid possible deadlocks.
257 # This avoids possible deadlocks when using the 'mirror' segment type.
258 # This setting determines whether LVs using the 'mirror' segment type
259 # are scanned for LVM labels. This affects the ability of mirrors to
260 # be used as physical volumes. If this setting is enabled, it is
261 # impossible to create VGs on top of mirror LVs, i.e. to stack VGs on
262 # mirror LVs. If this setting is disabled, allowing mirror LVs to be
263 # scanned, it may cause LVM processes and I/O to the mirror to become
264 # blocked. This is due to the way that the mirror segment type handles
265 # failures. In order for the hang to occur, an LVM command must be run
266 # just after a failure and before the automatic LVM repair process
267 # takes place, or there must be failures in multiple mirrors in the
268 # same VG at the same time with write failures occurring moments before
269 # a scan of the mirror's labels. The 'mirror' scanning problems do not
270 # apply to LVM RAID types like 'raid1' which handle failures in a
271 # different way, making them a better choice for VG stacking.
272 ignore_lvm_mirrors = 1
274 # Configuration option devices/disable_after_error_count.
275 # Number of I/O errors after which a device is skipped.
276 # During each LVM operation, errors received from each device are
277 # counted. If the counter of a device exceeds the limit set here,
278 # no further I/O is sent to that device for the remainder of the
279 # operation. Setting this to 0 disables the counters altogether.
280 disable_after_error_count = 0
282 # Configuration option devices/require_restorefile_with_uuid.
283 # Allow use of pvcreate --uuid without requiring --restorefile.
284 require_restorefile_with_uuid = 1
286 # Configuration option devices/pv_min_size.
287 # Minimum size in KiB of block devices which can be used as PVs.
288 # In a clustered environment all nodes must use the same value.
289 # Any value smaller than 512KiB is ignored. The previous built-in
293 # Configuration option devices/issue_discards.
294 # Issue discards to PVs that are no longer used by an LV.
295 # Discards are sent to an LV's underlying physical volumes when the LV
296 # is no longer using the physical volumes' space, e.g. lvremove,
297 # lvreduce. Discards inform the storage that a region is no longer
298 # used. Storage that supports discards advertise the protocol-specific
299 # way discards should be issued by the kernel (TRIM, UNMAP, or
300 # WRITE SAME with UNMAP bit set). Not all storage will support or
301 # benefit from discards, but SSDs and thinly provisioned LUNs
302 # generally do. If enabled, discards will only be issued if both the
303 # storage and kernel provide support.
306 # Configuration option devices/allow_changes_with_duplicate_pvs.
307 # Allow VG modification while a PV appears on multiple devices.
308 # When a PV appears on multiple devices, LVM attempts to choose the
309 # best device to use for the PV. If the devices represent the same
310 # underlying storage, the choice has minimal consequence. If the
311 # devices represent different underlying storage, the wrong choice
312 # can result in data loss if the VG is modified. Disabling this
313 # setting is the safest option because it prevents modifying a VG
314 # or activating LVs in it while a PV appears on multiple devices.
315 # Enabling this setting allows the VG to be used as usual even with
317 allow_changes_with_duplicate_pvs = 0
320 # Configuration section allocation.
321 # How LVM selects space and applies properties to LVs.
324 # Configuration option allocation/cling_tag_list.
325 # Advise LVM which PVs to use when searching for new space.
326 # When searching for free space to extend an LV, the 'cling' allocation
327 # policy will choose space on the same PVs as the last segment of the
328 # existing LV. If there is insufficient space and a list of tags is
329 # defined here, it will check whether any of them are attached to the
330 # PVs concerned and then seek to match those PV tags between existing
331 # extents and new extents.
334 # Use the special tag "@*" as a wildcard to match any PV tag:
335 # cling_tag_list = [ "@*" ]
336 # LVs are mirrored between two sites within a single VG, and
337 # PVs are tagged with either @site1 or @site2 to indicate where
339 # cling_tag_list = [ "@site1", "@site2" ]
341 # This configuration option does not have a default value defined.
343 # Configuration option allocation/maximise_cling.
344 # Use a previous allocation algorithm.
345 # Changes made in version 2.02.85 extended the reach of the 'cling'
346 # policies to detect more situations where data can be grouped onto
347 # the same disks. This setting can be used to disable the changes
348 # and revert to the previous algorithm.
351 # Configuration option allocation/use_blkid_wiping.
352 # Use blkid to detect existing signatures on new PVs and LVs.
353 # The blkid library can detect more signatures than the native LVM
354 # detection code, but may take longer. LVM needs to be compiled with
355 # blkid wiping support for this setting to apply. LVM native detection
356 # code is currently able to recognize: MD device signatures,
357 # swap signature, and LUKS signatures. To see the list of signatures
358 # recognized by blkid, check the output of the 'blkid -k' command.
361 # Configuration option allocation/wipe_signatures_when_zeroing_new_lvs.
362 # Look for and erase any signatures while zeroing a new LV.
363 # The --wipesignatures option overrides this setting.
364 # Zeroing is controlled by the -Z/--zero option, and if not specified,
365 # zeroing is used by default if possible. Zeroing simply overwrites the
366 # first 4KiB of a new LV with zeroes and does no signature detection or
367 # wiping. Signature wiping goes beyond zeroing and detects exact types
368 # and positions of signatures within the whole LV. It provides a
369 # cleaner LV after creation as all known signatures are wiped. The LV
370 # is not claimed incorrectly by other tools because of old signatures
371 # from previous use. The number of signatures that LVM can detect
372 # depends on the detection code that is selected (see
373 # use_blkid_wiping.) Wiping each detected signature must be confirmed.
374 # When this setting is disabled, signatures on new LVs are not detected
375 # or erased unless the --wipesignatures option is used directly.
376 wipe_signatures_when_zeroing_new_lvs = 1
378 # Configuration option allocation/mirror_logs_require_separate_pvs.
379 # Mirror logs and images will always use different PVs.
380 # The default setting changed in version 2.02.85.
381 mirror_logs_require_separate_pvs = 0
383 # Configuration option allocation/raid_stripe_all_devices.
384 # Stripe across all PVs when RAID stripes are not specified.
385 # If enabled, all PVs in the VG or on the command line are used for raid0/4/5/6/10
386 # when the command does not specify the number of stripes to use.
387 # This was the default behaviour until release 2.02.162.
388 # This configuration option has an automatic default value.
389 # raid_stripe_all_devices = 0
391 # Configuration option allocation/cache_pool_metadata_require_separate_pvs.
392 # Cache pool metadata and data will always use different PVs.
393 cache_pool_metadata_require_separate_pvs = 0
395 # Configuration option allocation/cache_mode.
396 # The default cache mode used for new cache.
400 # Data blocks are immediately written from the cache to disk.
402 # Data blocks are written from the cache back to disk after some
403 # delay to improve performance.
405 # This setting replaces allocation/cache_pool_cachemode.
406 # This configuration option has an automatic default value.
407 # cache_mode = "writethrough"
409 # Configuration option allocation/cache_policy.
410 # The default cache policy used for new cache volume.
411 # Since kernel 4.2 the default policy is smq (Stochastic multique),
412 # otherwise the older mq (Multiqueue) policy is selected.
413 # This configuration option does not have a default value defined.
415 # Configuration section allocation/cache_settings.
416 # Settings for the cache policy.
417 # See documentation for individual cache policies for more info.
418 # This configuration section has an automatic default value.
422 # Configuration option allocation/cache_pool_chunk_size.
423 # The minimal chunk size in KiB for cache pool volumes.
424 # Using a chunk_size that is too large can result in wasteful use of
425 # the cache, where small reads and writes can cause large sections of
426 # an LV to be mapped into the cache. However, choosing a chunk_size
427 # that is too small can result in more overhead trying to manage the
428 # numerous chunks that become mapped into the cache. The former is
429 # more of a problem than the latter in most cases, so the default is
430 # on the smaller end of the spectrum. Supported values range from
431 # 32KiB to 1GiB in multiples of 32.
432 # This configuration option does not have a default value defined.
434 # Configuration option allocation/cache_pool_max_chunks.
435 # The maximum number of chunks in a cache pool.
436 # For cache target v1.9 the recommended maximumm is 1000000 chunks.
437 # Using cache pool with more chunks may degrade cache performance.
438 # This configuration option does not have a default value defined.
440 # Configuration option allocation/thin_pool_metadata_require_separate_pvs.
441 # Thin pool metdata and data will always use different PVs.
442 thin_pool_metadata_require_separate_pvs = 0
444 # Configuration option allocation/thin_pool_zero.
445 # Thin pool data chunks are zeroed before they are first used.
446 # Zeroing with a larger thin pool chunk size reduces performance.
447 # This configuration option has an automatic default value.
450 # Configuration option allocation/thin_pool_discards.
451 # The discards behaviour of thin pool volumes.
458 # This configuration option has an automatic default value.
459 # thin_pool_discards = "passdown"
461 # Configuration option allocation/thin_pool_chunk_size_policy.
462 # The chunk size calculation policy for thin pool volumes.
466 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
467 # the chunk size based on estimation and device hints exposed in
468 # sysfs - the minimum_io_size. The chunk size is always at least
471 # If thin_pool_chunk_size is defined, use it. Otherwise, calculate
472 # the chunk size for performance based on device hints exposed in
473 # sysfs - the optimal_io_size. The chunk size is always at least
476 # This configuration option has an automatic default value.
477 # thin_pool_chunk_size_policy = "generic"
479 # Configuration option allocation/thin_pool_chunk_size.
480 # The minimal chunk size in KiB for thin pool volumes.
481 # Larger chunk sizes may improve performance for plain thin volumes,
482 # however using them for snapshot volumes is less efficient, as it
483 # consumes more space and takes extra time for copying. When unset,
484 # lvm tries to estimate chunk size starting from 64KiB. Supported
485 # values are in the range 64KiB to 1GiB.
486 # This configuration option does not have a default value defined.
488 # Configuration option allocation/physical_extent_size.
489 # Default physical extent size in KiB to use for new VGs.
490 # This configuration option has an automatic default value.
491 # physical_extent_size = 4096
494 # Configuration section log.
495 # How LVM log information is reported.
498 # Configuration option log/report_command_log.
499 # Enable or disable LVM log reporting.
500 # If enabled, LVM will collect a log of operations, messages,
501 # per-object return codes with object identification and associated
502 # error numbers (errnos) during LVM command processing. Then the
503 # log is either reported solely or in addition to any existing
504 # reports, depending on LVM command used. If it is a reporting command
505 # (e.g. pvs, vgs, lvs, lvm fullreport), then the log is reported in
506 # addition to any existing reports. Otherwise, there's only log report
507 # on output. For all applicable LVM commands, you can request that
508 # the output has only log report by using --logonly command line
509 # option. Use log/command_log_cols and log/command_log_sort settings
510 # to define fields to display and sort fields for the log report.
511 # You can also use log/command_log_selection to define selection
512 # criteria used each time the log is reported.
513 # This configuration option has an automatic default value.
514 # report_command_log = 0
516 # Configuration option log/command_log_sort.
517 # List of columns to sort by when reporting command log.
518 # See <lvm command> --logonly --configreport log -o help
519 # for the list of possible fields.
520 # This configuration option has an automatic default value.
521 # command_log_sort = "log_seq_num"
523 # Configuration option log/command_log_cols.
524 # List of columns to report when reporting command log.
525 # See <lvm command> --logonly --configreport log -o help
526 # for the list of possible fields.
527 # This configuration option has an automatic default value.
528 # 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"
530 # Configuration option log/command_log_selection.
531 # Selection criteria used when reporting command log.
532 # You can define selection criteria that are applied each
533 # time log is reported. This way, it is possible to control the
534 # amount of log that is displayed on output and you can select
535 # only parts of the log that are important for you. To define
536 # selection criteria, use fields from log report. See also
537 # <lvm command> --logonly --configreport log -S help for the
538 # list of possible fields and selection operators. You can also
539 # define selection criteria for log report on command line directly
540 # using <lvm command> --configreport log -S <selection criteria>
541 # which has precedence over log/command_log_selection setting.
542 # For more information about selection criteria in general, see
544 # This configuration option has an automatic default value.
545 # command_log_selection = "!(log_type=status && message=success)"
547 # Configuration option log/verbose.
548 # Controls the messages sent to stdout or stderr.
551 # Configuration option log/silent.
552 # Suppress all non-essential messages from stdout.
553 # This has the same effect as -qq. When enabled, the following commands
554 # still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck,
555 # pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs.
556 # Non-essential messages are shifted from log level 4 to log level 5
557 # for syslog and lvm2_log_fn purposes.
558 # Any 'yes' or 'no' questions not overridden by other arguments are
559 # suppressed and default to 'no'.
562 # Configuration option log/syslog.
563 # Send log messages through syslog.
566 # Configuration option log/file.
567 # Write error and debug log messages to a file specified here.
568 # This configuration option does not have a default value defined.
570 # Configuration option log/overwrite.
571 # Overwrite the log file each time the program is run.
574 # Configuration option log/level.
575 # The level of log messages that are sent to the log file or syslog.
576 # There are 6 syslog-like log levels currently in use: 2 to 7 inclusive.
577 # 7 is the most verbose (LOG_DEBUG).
580 # Configuration option log/indent.
581 # Indent messages according to their severity.
584 # Configuration option log/command_names.
585 # Display the command name on each line of output.
588 # Configuration option log/prefix.
589 # A prefix to use before the log message text.
590 # (After the command name, if selected).
591 # Two spaces allows you to see/grep the severity of each message.
592 # To make the messages look similar to the original LVM tools use:
593 # indent = 0, command_names = 1, prefix = " -- "
596 # Configuration option log/activation.
597 # Log messages during activation.
598 # Don't use this in low memory situations (can deadlock).
601 # Configuration option log/debug_classes.
602 # Select log messages by class.
603 # Some debugging messages are assigned to a class and only appear in
604 # debug output if the class is listed here. Classes currently
605 # available: memory, devices, activation, allocation, lvmetad,
606 # metadata, cache, locking, lvmpolld. Use "all" to see everything.
607 debug_classes = [ "memory", "devices", "activation", "allocation", "lvmetad", "metadata", "cache", "locking", "lvmpolld", "dbus" ]
610 # Configuration section backup.
611 # How LVM metadata is backed up and archived.
612 # In LVM, a 'backup' is a copy of the metadata for the current system,
613 # and an 'archive' contains old metadata configurations. They are
614 # stored in a human readable text format.
617 # Configuration option backup/backup.
618 # Maintain a backup of the current metadata configuration.
619 # Think very hard before turning this off!
622 # Configuration option backup/backup_dir.
623 # Location of the metadata backup files.
624 # Remember to back up this directory regularly!
625 backup_dir = "/etc/lvm/backup"
627 # Configuration option backup/archive.
628 # Maintain an archive of old metadata configurations.
629 # Think very hard before turning this off.
632 # Configuration option backup/archive_dir.
633 # Location of the metdata archive files.
634 # Remember to back up this directory regularly!
635 archive_dir = "/etc/lvm/archive"
637 # Configuration option backup/retain_min.
638 # Minimum number of archives to keep.
641 # Configuration option backup/retain_days.
642 # Minimum number of days to keep archive files.
646 # Configuration section shell.
647 # Settings for running LVM in shell (readline) mode.
650 # Configuration option shell/history_size.
651 # Number of lines of history to store in ~/.lvm_history.
655 # Configuration section global.
656 # Miscellaneous global LVM settings.
659 # Configuration option global/umask.
660 # The file creation mask for any files and directories created.
661 # Interpreted as octal if the first digit is zero.
664 # Configuration option global/test.
665 # No on-disk metadata changes will be made in test mode.
666 # Equivalent to having the -t option on every command.
669 # Configuration option global/units.
670 # Default value for --units argument.
673 # Configuration option global/si_unit_consistency.
674 # Distinguish between powers of 1024 and 1000 bytes.
675 # The LVM commands distinguish between powers of 1024 bytes,
676 # e.g. KiB, MiB, GiB, and powers of 1000 bytes, e.g. KB, MB, GB.
677 # If scripts depend on the old behaviour, disable this setting
678 # temporarily until they are updated.
679 si_unit_consistency = 1
681 # Configuration option global/suffix.
682 # Display unit suffix for sizes.
683 # This setting has no effect if the units are in human-readable form
684 # (global/units = "h") in which case the suffix is always displayed.
687 # Configuration option global/activation.
688 # Enable/disable communication with the kernel device-mapper.
689 # Disable to use the tools to manipulate LVM metadata without
690 # activating any logical volumes. If the device-mapper driver
691 # is not present in the kernel, disabling this should suppress
692 # the error messages.
695 # Configuration option global/fallback_to_lvm1.
696 # Try running LVM1 tools if LVM cannot communicate with DM.
697 # This option only applies to 2.4 kernels and is provided to help
698 # switch between device-mapper kernels and LVM1 kernels. The LVM1
699 # tools need to be installed with .lvm1 suffices, e.g. vgscan.lvm1.
700 # They will stop working once the lvm2 on-disk metadata format is used.
701 # This configuration option has an automatic default value.
702 # fallback_to_lvm1 = 0
704 # Configuration option global/format.
705 # The default metadata format that commands should use.
706 # The -M 1|2 option overrides this setting.
712 # This configuration option has an automatic default value.
715 # Configuration option global/format_libraries.
716 # Shared libraries that process different metadata formats.
717 # If support for LVM1 metadata was compiled as a shared library use
718 # format_libraries = "liblvm2format1.so"
719 # This configuration option does not have a default value defined.
721 # Configuration option global/segment_libraries.
722 # This configuration option does not have a default value defined.
724 # Configuration option global/proc.
725 # Location of proc filesystem.
726 # This configuration option is advanced.
729 # Configuration option global/etc.
730 # Location of /etc system configuration directory.
733 # Configuration option global/locking_type.
734 # Type of locking to use.
738 # Turns off locking. Warning: this risks metadata corruption if
739 # commands run concurrently.
741 # LVM uses local file-based locking, the standard mode.
743 # LVM uses the external shared library locking_library.
745 # LVM uses built-in clustered locking with clvmd.
746 # This is incompatible with lvmetad. If use_lvmetad is enabled,
747 # LVM prints a warning and disables lvmetad use.
749 # LVM uses read-only locking which forbids any operations that
750 # might change metadata.
752 # Offers dummy locking for tools that do not need any locks.
753 # You should not need to set this directly; the tools will select
754 # when to use it instead of the configured locking_type.
755 # Do not use lvmetad or the kernel device-mapper driver with this
756 # locking type. It is used by the --readonly option that offers
757 # read-only access to Volume Group metadata that cannot be locked
758 # safely because it belongs to an inaccessible domain and might be
759 # in use, for example a virtual machine image or a disk that is
760 # shared by a clustered machine.
764 # Configuration option global/wait_for_locks.
765 # When disabled, fail if a lock request would block.
768 # Configuration option global/fallback_to_clustered_locking.
769 # Attempt to use built-in cluster locking if locking_type 2 fails.
770 # If using external locking (type 2) and initialisation fails, with
771 # this enabled, an attempt will be made to use the built-in clustered
772 # locking. Disable this if using a customised locking_library.
773 fallback_to_clustered_locking = 1
775 # Configuration option global/fallback_to_local_locking.
776 # Use locking_type 1 (local) if locking_type 2 or 3 fail.
777 # If an attempt to initialise type 2 or type 3 locking failed, perhaps
778 # because cluster components such as clvmd are not running, with this
779 # enabled, an attempt will be made to use local file-based locking
780 # (type 1). If this succeeds, only commands against local VGs will
781 # proceed. VGs marked as clustered will be ignored.
782 fallback_to_local_locking = 1
784 # Configuration option global/locking_dir.
785 # Directory to use for LVM command file locks.
786 # Local non-LV directory that holds file-based locks while commands are
787 # in progress. A directory like /tmp that may get wiped on reboot is OK.
788 locking_dir = "/run/lock/lvm"
790 # Configuration option global/prioritise_write_locks.
791 # Allow quicker VG write access during high volume read access.
792 # When there are competing read-only and read-write access requests for
793 # a volume group's metadata, instead of always granting the read-only
794 # requests immediately, delay them to allow the read-write requests to
795 # be serviced. Without this setting, write access may be stalled by a
796 # high volume of read-only requests. This option only affects
797 # locking_type 1 viz. local file-based locking.
798 prioritise_write_locks = 1
800 # Configuration option global/library_dir.
801 # Search this directory first for shared libraries.
802 # This configuration option does not have a default value defined.
804 # Configuration option global/locking_library.
805 # The external locking library to use for locking_type 2.
806 # This configuration option has an automatic default value.
807 # locking_library = "liblvm2clusterlock.so"
809 # Configuration option global/abort_on_internal_errors.
810 # Abort a command that encounters an internal error.
811 # Treat any internal errors as fatal errors, aborting the process that
812 # encountered the internal error. Please only enable for debugging.
813 abort_on_internal_errors = 0
815 # Configuration option global/detect_internal_vg_cache_corruption.
816 # Internal verification of VG structures.
817 # Check if CRC matches when a parsed VG is used multiple times. This
818 # is useful to catch unexpected changes to cached VG structures.
819 # Please only enable for debugging.
820 detect_internal_vg_cache_corruption = 0
822 # Configuration option global/metadata_read_only.
823 # No operations that change on-disk metadata are permitted.
824 # Additionally, read-only commands that encounter metadata in need of
825 # repair will still be allowed to proceed exactly as if the repair had
826 # been performed (except for the unchanged vg_seqno). Inappropriate
827 # use could mess up your system, so seek advice first!
828 metadata_read_only = 0
830 # Configuration option global/mirror_segtype_default.
831 # The segment type used by the short mirroring option -m.
832 # The --type mirror|raid1 option overrides this setting.
836 # The original RAID1 implementation from LVM/DM. It is
837 # characterized by a flexible log solution (core, disk, mirrored),
838 # and by the necessity to block I/O while handling a failure.
839 # There is an inherent race in the dmeventd failure handling logic
840 # with snapshots of devices using this type of RAID1 that in the
841 # worst case could cause a deadlock. (Also see
842 # devices/ignore_lvm_mirrors.)
844 # This is a newer RAID1 implementation using the MD RAID1
845 # personality through device-mapper. It is characterized by a
846 # lack of log options. (A log is always allocated for every
847 # device and they are placed on the same device as the image,
848 # so no separate devices are required.) This mirror
849 # implementation does not require I/O to be blocked while
850 # handling a failure. This mirror implementation is not
851 # cluster-aware and cannot be used in a shared (active/active)
852 # fashion in a cluster.
854 mirror_segtype_default = "raid1"
856 # Configuration option global/raid10_segtype_default.
857 # The segment type used by the -i -m combination.
858 # The --type raid10|mirror option overrides this setting.
859 # The --stripes/-i and --mirrors/-m options can both be specified
860 # during the creation of a logical volume to use both striping and
861 # mirroring for the LV. There are two different implementations.
865 # LVM uses MD's RAID10 personality through DM. This is the
868 # LVM layers the 'mirror' and 'stripe' segment types. The layering
869 # is done by creating a mirror LV on top of striped sub-LVs,
870 # effectively creating a RAID 0+1 array. The layering is suboptimal
871 # in terms of providing redundancy and performance.
873 raid10_segtype_default = "raid10"
875 # Configuration option global/sparse_segtype_default.
876 # The segment type used by the -V -L combination.
877 # The --type snapshot|thin option overrides this setting.
878 # The combination of -V and -L options creates a sparse LV. There are
879 # two different implementations.
883 # The original snapshot implementation from LVM/DM. It uses an old
884 # snapshot that mixes data and metadata within a single COW
885 # storage volume and performs poorly when the size of stored data
886 # passes hundreds of MB.
888 # A newer implementation that uses thin provisioning. It has a
889 # bigger minimal chunk size (64KiB) and uses a separate volume for
890 # metadata. It has better performance, especially when more data
891 # is used. It also supports full snapshots.
893 sparse_segtype_default = "thin"
895 # Configuration option global/lvdisplay_shows_full_device_path.
896 # Enable this to reinstate the previous lvdisplay name format.
897 # The default format for displaying LV names in lvdisplay was changed
898 # in version 2.02.89 to show the LV name and path separately.
899 # Previously this was always shown as /dev/vgname/lvname even when that
900 # was never a valid path in the /dev filesystem.
901 # This configuration option has an automatic default value.
902 # lvdisplay_shows_full_device_path = 0
904 # Configuration option global/use_lvmetad.
905 # Use lvmetad to cache metadata and reduce disk scanning.
906 # When enabled (and running), lvmetad provides LVM commands with VG
907 # metadata and PV state. LVM commands then avoid reading this
908 # information from disks which can be slow. When disabled (or not
909 # running), LVM commands fall back to scanning disks to obtain VG
910 # metadata. lvmetad is kept updated via udev rules which must be set
911 # up for LVM to work correctly. (The udev rules should be installed
912 # by default.) Without a proper udev setup, changes in the system's
913 # block device configuration will be unknown to LVM, and ignored
914 # until a manual 'pvscan --cache' is run. If lvmetad was running
915 # while use_lvmetad was disabled, it must be stopped, use_lvmetad
916 # enabled, and then started. When using lvmetad, LV activation is
917 # switched to an automatic, event-based mode. In this mode, LVs are
918 # activated based on incoming udev events that inform lvmetad when
919 # PVs appear on the system. When a VG is complete (all PVs present),
920 # it is auto-activated. The auto_activation_volume_list setting
921 # controls which LVs are auto-activated (all by default.)
922 # When lvmetad is updated (automatically by udev events, or directly
923 # by pvscan --cache), devices/filter is ignored and all devices are
924 # scanned by default. lvmetad always keeps unfiltered information
925 # which is provided to LVM commands. Each LVM command then filters
926 # based on devices/filter. This does not apply to other, non-regexp,
927 # filtering settings: component filters such as multipath and MD
928 # are checked during pvscan --cache. To filter a device and prevent
929 # scanning from the LVM system entirely, including lvmetad, use
930 # devices/global_filter.
933 # Configuration option global/lvmetad_update_wait_time.
934 # The number of seconds a command will wait for lvmetad update to finish.
935 # After waiting for this period, a command will not use lvmetad, and
936 # will revert to disk scanning.
937 # This configuration option has an automatic default value.
938 # lvmetad_update_wait_time = 10
940 # Configuration option global/use_lvmlockd.
941 # Use lvmlockd for locking among hosts using LVM on shared storage.
942 # Applicable only if LVM is compiled with lockd support in which
943 # case there is also lvmlockd(8) man page available for more
947 # Configuration option global/lvmlockd_lock_retries.
948 # Retry lvmlockd lock requests this many times.
949 # Applicable only if LVM is compiled with lockd support
950 # This configuration option has an automatic default value.
951 # lvmlockd_lock_retries = 3
953 # Configuration option global/sanlock_lv_extend.
954 # Size in MiB to extend the internal LV holding sanlock locks.
955 # The internal LV holds locks for each LV in the VG, and after enough
956 # LVs have been created, the internal LV needs to be extended. lvcreate
957 # will automatically extend the internal LV when needed by the amount
958 # specified here. Setting this to 0 disables the automatic extension
959 # and can cause lvcreate to fail. Applicable only if LVM is compiled
961 # This configuration option has an automatic default value.
962 # sanlock_lv_extend = 256
964 # Configuration option global/thin_check_executable.
965 # The full path to the thin_check command.
966 # LVM uses this command to check that a thin metadata device is in a
967 # usable state. When a thin pool is activated and after it is
968 # deactivated, this command is run. Activation will only proceed if
969 # the command has an exit status of 0. Set to "" to skip this check.
970 # (Not recommended.) Also see thin_check_options.
971 # (See package device-mapper-persistent-data or thin-provisioning-tools)
972 # This configuration option has an automatic default value.
973 # thin_check_executable = "/usr/sbin/thin_check"
975 # Configuration option global/thin_dump_executable.
976 # The full path to the thin_dump command.
977 # LVM uses this command to dump thin pool metadata.
978 # (See package device-mapper-persistent-data or thin-provisioning-tools)
979 # This configuration option has an automatic default value.
980 # thin_dump_executable = "/usr/sbin/thin_dump"
982 # Configuration option global/thin_repair_executable.
983 # The full path to the thin_repair command.
984 # LVM uses this command to repair a thin metadata device if it is in
985 # an unusable state. Also see thin_repair_options.
986 # (See package device-mapper-persistent-data or thin-provisioning-tools)
987 # This configuration option has an automatic default value.
988 # thin_repair_executable = "/usr/sbin/thin_repair"
990 # Configuration option global/thin_check_options.
991 # List of options passed to the thin_check command.
992 # With thin_check version 2.1 or newer you can add the option
993 # --ignore-non-fatal-errors to let it pass through ignorable errors
994 # and fix them later. With thin_check version 3.2 or newer you should
995 # include the option --clear-needs-check-flag.
996 # This configuration option has an automatic default value.
997 # thin_check_options = [ "-q", "--clear-needs-check-flag" ]
999 # Configuration option global/thin_repair_options.
1000 # List of options passed to the thin_repair command.
1001 # This configuration option has an automatic default value.
1002 # thin_repair_options = [ "" ]
1004 # Configuration option global/thin_disabled_features.
1005 # Features to not use in the thin driver.
1006 # This can be helpful for testing, or to avoid using a feature that is
1007 # causing problems. Features include: block_size, discards,
1008 # discards_non_power_2, external_origin, metadata_resize,
1009 # external_origin_extend, error_if_no_space.
1012 # thin_disabled_features = [ "discards", "block_size" ]
1014 # This configuration option does not have a default value defined.
1016 # Configuration option global/cache_disabled_features.
1017 # Features to not use in the cache driver.
1018 # This can be helpful for testing, or to avoid using a feature that is
1019 # causing problems. Features include: policy_mq, policy_smq.
1022 # cache_disabled_features = [ "policy_smq" ]
1024 # This configuration option does not have a default value defined.
1026 # Configuration option global/cache_check_executable.
1027 # The full path to the cache_check command.
1028 # LVM uses this command to check that a cache metadata device is in a
1029 # usable state. When a cached LV is activated and after it is
1030 # deactivated, this command is run. Activation will only proceed if the
1031 # command has an exit status of 0. Set to "" to skip this check.
1032 # (Not recommended.) Also see cache_check_options.
1033 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1034 # This configuration option has an automatic default value.
1035 # cache_check_executable = "/usr/sbin/cache_check"
1037 # Configuration option global/cache_dump_executable.
1038 # The full path to the cache_dump command.
1039 # LVM uses this command to dump cache pool metadata.
1040 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1041 # This configuration option has an automatic default value.
1042 # cache_dump_executable = "/usr/sbin/cache_dump"
1044 # Configuration option global/cache_repair_executable.
1045 # The full path to the cache_repair command.
1046 # LVM uses this command to repair a cache metadata device if it is in
1047 # an unusable state. Also see cache_repair_options.
1048 # (See package device-mapper-persistent-data or thin-provisioning-tools)
1049 # This configuration option has an automatic default value.
1050 # cache_repair_executable = "/usr/sbin/cache_repair"
1052 # Configuration option global/cache_check_options.
1053 # List of options passed to the cache_check command.
1054 # With cache_check version 5.0 or newer you should include the option
1055 # --clear-needs-check-flag.
1056 # This configuration option has an automatic default value.
1057 # cache_check_options = [ "-q", "--clear-needs-check-flag" ]
1059 # Configuration option global/cache_repair_options.
1060 # List of options passed to the cache_repair command.
1061 # This configuration option has an automatic default value.
1062 # cache_repair_options = [ "" ]
1064 # Configuration option global/system_id_source.
1065 # The method LVM uses to set the local system ID.
1066 # Volume Groups can also be given a system ID (by vgcreate, vgchange,
1067 # or vgimport.) A VG on shared storage devices is accessible only to
1068 # the host with a matching system ID. See 'man lvmsystemid' for
1069 # information on limitations and correct usage.
1073 # The host has no system ID.
1075 # Obtain the system ID from the system_id setting in the 'local'
1076 # section of an lvm configuration file, e.g. lvmlocal.conf.
1078 # Set the system ID from the hostname (uname) of the system.
1079 # System IDs beginning localhost are not permitted.
1081 # Use the contents of the machine-id file to set the system ID.
1082 # Some systems create this file at installation time.
1083 # See 'man machine-id' and global/etc.
1085 # Use the contents of another file (system_id_file) to set the
1088 system_id_source = "none"
1090 # Configuration option global/system_id_file.
1091 # The full path to the file containing a system ID.
1092 # This is used when system_id_source is set to 'file'.
1093 # Comments starting with the character # are ignored.
1094 # This configuration option does not have a default value defined.
1096 # Configuration option global/use_lvmpolld.
1097 # Use lvmpolld to supervise long running LVM commands.
1098 # When enabled, control of long running LVM commands is transferred
1099 # from the original LVM command to the lvmpolld daemon. This allows
1100 # the operation to continue independent of the original LVM command.
1101 # After lvmpolld takes over, the LVM command displays the progress
1102 # of the ongoing operation. lvmpolld itself runs LVM commands to
1103 # manage the progress of ongoing operations. lvmpolld can be used as
1104 # a native systemd service, which allows it to be started on demand,
1105 # and to use its own control group. When this option is disabled, LVM
1106 # commands will supervise long running operations by forking themselves.
1107 # Applicable only if LVM is compiled with lvmpolld support.
1110 # Configuration option global/notify_dbus.
1111 # Enable D-Bus notification from LVM commands.
1112 # When enabled, an LVM command that changes PVs, changes VG metadata,
1113 # or changes the activation state of an LV will send a notification.
1117 # Configuration section activation.
1120 # Configuration option activation/checks.
1121 # Perform internal checks of libdevmapper operations.
1122 # Useful for debugging problems with activation. Some of the checks may
1123 # be expensive, so it's best to use this only when there seems to be a
1127 # Configuration option activation/udev_sync.
1128 # Use udev notifications to synchronize udev and LVM.
1129 # The --nodevsync option overrides this setting.
1130 # When disabled, LVM commands will not wait for notifications from
1131 # udev, but continue irrespective of any possible udev processing in
1132 # the background. Only use this if udev is not running or has rules
1133 # that ignore the devices LVM creates. If enabled when udev is not
1134 # running, and LVM processes are waiting for udev, run the command
1135 # 'dmsetup udevcomplete_all' to wake them up.
1138 # Configuration option activation/udev_rules.
1139 # Use udev rules to manage LV device nodes and symlinks.
1140 # When disabled, LVM will manage the device nodes and symlinks for
1141 # active LVs itself. Manual intervention may be required if this
1142 # setting is changed while LVs are active.
1145 # Configuration option activation/verify_udev_operations.
1146 # Use extra checks in LVM to verify udev operations.
1147 # This enables additional checks (and if necessary, repairs) on entries
1148 # in the device directory after udev has completed processing its
1149 # events. Useful for diagnosing problems with LVM/udev interactions.
1150 verify_udev_operations = 0
1152 # Configuration option activation/retry_deactivation.
1153 # Retry failed LV deactivation.
1154 # If LV deactivation fails, LVM will retry for a few seconds before
1155 # failing. This may happen because a process run from a quick udev rule
1156 # temporarily opened the device.
1157 retry_deactivation = 1
1159 # Configuration option activation/missing_stripe_filler.
1160 # Method to fill missing stripes when activating an incomplete LV.
1161 # Using 'error' will make inaccessible parts of the device return I/O
1162 # errors on access. You can instead use a device path, in which case,
1163 # that device will be used in place of missing stripes. Using anything
1164 # other than 'error' with mirrored or snapshotted volumes is likely to
1165 # result in data corruption.
1166 # This configuration option is advanced.
1167 missing_stripe_filler = "error"
1169 # Configuration option activation/use_linear_target.
1170 # Use the linear target to optimize single stripe LVs.
1171 # When disabled, the striped target is used. The linear target is an
1172 # optimised version of the striped target that only handles a single
1174 use_linear_target = 1
1176 # Configuration option activation/reserved_stack.
1177 # Stack size in KiB to reserve for use while devices are suspended.
1178 # Insufficent reserve risks I/O deadlock during device suspension.
1181 # Configuration option activation/reserved_memory.
1182 # Memory size in KiB to reserve for use while devices are suspended.
1183 # Insufficent reserve risks I/O deadlock during device suspension.
1184 reserved_memory = 8192
1186 # Configuration option activation/process_priority.
1187 # Nice value used while devices are suspended.
1188 # Use a high priority so that LVs are suspended
1189 # for the shortest possible time.
1190 process_priority = -18
1192 # Configuration option activation/volume_list.
1193 # Only LVs selected by this list are activated.
1194 # If this list is defined, an LV is only activated if it matches an
1195 # entry in this list. If this list is undefined, it imposes no limits
1196 # on LV activation (all are allowed).
1200 # The VG name is matched exactly and selects all LVs in the VG.
1202 # The VG name and LV name are matched exactly and selects the LV.
1204 # Selects an LV if the specified tag matches a tag set on the LV
1207 # Selects an LV if a tag defined on the host is also set on the LV
1208 # or VG. See tags/hosttags. If any host tags exist but volume_list
1209 # is not defined, a default single-entry list containing '@*'
1213 # volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1215 # This configuration option does not have a default value defined.
1217 # Configuration option activation/auto_activation_volume_list.
1218 # Only LVs selected by this list are auto-activated.
1219 # This list works like volume_list, but it is used only by
1220 # auto-activation commands. It does not apply to direct activation
1221 # commands. If this list is defined, an LV is only auto-activated
1222 # if it matches an entry in this list. If this list is undefined, it
1223 # imposes no limits on LV auto-activation (all are allowed.) If this
1224 # list is defined and empty, i.e. "[]", then no LVs are selected for
1225 # auto-activation. An LV that is selected by this list for
1226 # auto-activation, must also be selected by volume_list (if defined)
1227 # before it is activated. Auto-activation is an activation command that
1228 # includes the 'a' argument: --activate ay or -a ay. The 'a' (auto)
1229 # argument for auto-activation is meant to be used by activation
1230 # commands that are run automatically by the system, as opposed to LVM
1231 # commands run directly by a user. A user may also use the 'a' flag
1232 # directly to perform auto-activation. Also see pvscan(8) for more
1233 # information about auto-activation.
1237 # The VG name is matched exactly and selects all LVs in the VG.
1239 # The VG name and LV name are matched exactly and selects the LV.
1241 # Selects an LV if the specified tag matches a tag set on the LV
1244 # Selects an LV if a tag defined on the host is also set on the LV
1245 # or VG. See tags/hosttags. If any host tags exist but volume_list
1246 # is not defined, a default single-entry list containing '@*'
1250 # auto_activation_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1252 # This configuration option does not have a default value defined.
1254 # Configuration option activation/read_only_volume_list.
1255 # LVs in this list are activated in read-only mode.
1256 # If this list is defined, each LV that is to be activated is checked
1257 # against this list, and if it matches, it is activated in read-only
1258 # mode. This overrides the permission setting stored in the metadata,
1259 # e.g. from --permission rw.
1263 # The VG name is matched exactly and selects all LVs in the VG.
1265 # The VG name and LV name are matched exactly and selects the LV.
1267 # Selects an LV if the specified tag matches a tag set on the LV
1270 # Selects an LV if a tag defined on the host is also set on the LV
1271 # or VG. See tags/hosttags. If any host tags exist but volume_list
1272 # is not defined, a default single-entry list containing '@*'
1276 # read_only_volume_list = [ "vg1", "vg2/lvol1", "@tag1", "@*" ]
1278 # This configuration option does not have a default value defined.
1280 # Configuration option activation/raid_region_size.
1281 # Size in KiB of each raid or mirror synchronization region.
1282 # For raid or mirror segment types, this is the amount of data that is
1283 # copied at once when initializing, or moved at once by pvmove.
1284 raid_region_size = 512
1286 # Configuration option activation/error_when_full.
1287 # Return errors if a thin pool runs out of space.
1288 # The --errorwhenfull option overrides this setting.
1289 # When enabled, writes to thin LVs immediately return an error if the
1290 # thin pool is out of data space. When disabled, writes to thin LVs
1291 # are queued if the thin pool is out of space, and processed when the
1292 # thin pool data space is extended. New thin pools are assigned the
1293 # behavior defined here.
1294 # This configuration option has an automatic default value.
1295 # error_when_full = 0
1297 # Configuration option activation/readahead.
1298 # Setting to use when there is no readahead setting in metadata.
1302 # Disable readahead.
1304 # Use default value chosen by kernel.
1308 # Configuration option activation/raid_fault_policy.
1309 # Defines how a device failure in a RAID LV is handled.
1310 # This includes LVs that have the following segment types:
1311 # raid1, raid4, raid5*, and raid6*.
1312 # If a device in the LV fails, the policy determines the steps
1313 # performed by dmeventd automatically, and the steps perfomed by the
1314 # manual command lvconvert --repair --use-policies.
1315 # Automatic handling requires dmeventd to be monitoring the LV.
1319 # Use the system log to warn the user that a device in the RAID LV
1320 # has failed. It is left to the user to run lvconvert --repair
1321 # manually to remove or replace the failed device. As long as the
1322 # number of failed devices does not exceed the redundancy of the LV
1323 # (1 device for raid4/5, 2 for raid6), the LV will remain usable.
1325 # Attempt to use any extra physical volumes in the VG as spares and
1326 # replace faulty devices.
1328 raid_fault_policy = "warn"
1330 # Configuration option activation/mirror_image_fault_policy.
1331 # Defines how a device failure in a 'mirror' LV is handled.
1332 # An LV with the 'mirror' segment type is composed of mirror images
1333 # (copies) and a mirror log. A disk log ensures that a mirror LV does
1334 # not need to be re-synced (all copies made the same) every time a
1335 # machine reboots or crashes. If a device in the LV fails, this policy
1336 # determines the steps perfomed by dmeventd automatically, and the steps
1337 # performed by the manual command lvconvert --repair --use-policies.
1338 # Automatic handling requires dmeventd to be monitoring the LV.
1342 # Simply remove the faulty device and run without it. If the log
1343 # device fails, the mirror would convert to using an in-memory log.
1344 # This means the mirror will not remember its sync status across
1345 # crashes/reboots and the entire mirror will be re-synced. If a
1346 # mirror image fails, the mirror will convert to a non-mirrored
1347 # device if there is only one remaining good copy.
1349 # Remove the faulty device and try to allocate space on a new
1350 # device to be a replacement for the failed device. Using this
1351 # policy for the log is fast and maintains the ability to remember
1352 # sync state through crashes/reboots. Using this policy for a
1353 # mirror device is slow, as it requires the mirror to resynchronize
1354 # the devices, but it will preserve the mirror characteristic of
1355 # the device. This policy acts like 'remove' if no suitable device
1356 # and space can be allocated for the replacement.
1358 # Not yet implemented. Useful to place the log device temporarily
1359 # on the same physical volume as one of the mirror images. This
1360 # policy is not recommended for mirror devices since it would break
1361 # the redundant nature of the mirror. This policy acts like
1362 # 'remove' if no suitable device and space can be allocated for the
1365 mirror_image_fault_policy = "remove"
1367 # Configuration option activation/mirror_log_fault_policy.
1368 # Defines how a device failure in a 'mirror' log LV is handled.
1369 # The mirror_image_fault_policy description for mirrored LVs also
1370 # applies to mirrored log LVs.
1371 mirror_log_fault_policy = "allocate"
1373 # Configuration option activation/snapshot_autoextend_threshold.
1374 # Auto-extend a snapshot when its usage exceeds this percent.
1375 # Setting this to 100 disables automatic extension.
1376 # The minimum value is 50 (a smaller value is treated as 50.)
1377 # Also see snapshot_autoextend_percent.
1378 # Automatic extension requires dmeventd to be monitoring the LV.
1381 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1382 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1383 # 840M, it is extended to 1.44G:
1384 # snapshot_autoextend_threshold = 70
1386 snapshot_autoextend_threshold = 100
1388 # Configuration option activation/snapshot_autoextend_percent.
1389 # Auto-extending a snapshot adds this percent extra space.
1390 # The amount of additional space added to a snapshot is this
1391 # percent of its current size.
1394 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1395 # snapshot exceeds 700M, it is extended to 1.2G, and when it exceeds
1396 # 840M, it is extended to 1.44G:
1397 # snapshot_autoextend_percent = 20
1399 snapshot_autoextend_percent = 20
1401 # Configuration option activation/thin_pool_autoextend_threshold.
1402 # Auto-extend a thin pool when its usage exceeds this percent.
1403 # Setting this to 100 disables automatic extension.
1404 # The minimum value is 50 (a smaller value is treated as 50.)
1405 # Also see thin_pool_autoextend_percent.
1406 # Automatic extension requires dmeventd to be monitoring the LV.
1409 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1410 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1411 # 840M, it is extended to 1.44G:
1412 # thin_pool_autoextend_threshold = 70
1414 thin_pool_autoextend_threshold = 100
1416 # Configuration option activation/thin_pool_autoextend_percent.
1417 # Auto-extending a thin pool adds this percent extra space.
1418 # The amount of additional space added to a thin pool is this
1419 # percent of its current size.
1422 # Using 70% autoextend threshold and 20% autoextend size, when a 1G
1423 # thin pool exceeds 700M, it is extended to 1.2G, and when it exceeds
1424 # 840M, it is extended to 1.44G:
1425 # thin_pool_autoextend_percent = 20
1427 thin_pool_autoextend_percent = 20
1429 # Configuration option activation/mlock_filter.
1430 # Do not mlock these memory areas.
1431 # While activating devices, I/O to devices being (re)configured is
1432 # suspended. As a precaution against deadlocks, LVM pins memory it is
1433 # using so it is not paged out, and will not require I/O to reread.
1434 # Groups of pages that are known not to be accessed during activation
1435 # do not need to be pinned into memory. Each string listed in this
1436 # setting is compared against each line in /proc/self/maps, and the
1437 # pages corresponding to lines that match are not pinned. On some
1438 # systems, locale-archive was found to make up over 80% of the memory
1439 # used by the process.
1442 # mlock_filter = [ "locale/locale-archive", "gconv/gconv-modules.cache" ]
1444 # This configuration option is advanced.
1445 # This configuration option does not have a default value defined.
1447 # Configuration option activation/use_mlockall.
1448 # Use the old behavior of mlockall to pin all memory.
1449 # Prior to version 2.02.62, LVM used mlockall() to pin the whole
1450 # process's memory while activating devices.
1453 # Configuration option activation/monitoring.
1454 # Monitor LVs that are activated.
1455 # The --ignoremonitoring option overrides this setting.
1456 # When enabled, LVM will ask dmeventd to monitor activated LVs.
1459 # Configuration option activation/polling_interval.
1460 # Check pvmove or lvconvert progress at this interval (seconds).
1461 # When pvmove or lvconvert must wait for the kernel to finish
1462 # synchronising or merging data, they check and report progress at
1463 # intervals of this number of seconds. If this is set to 0 and there
1464 # is only one thing to wait for, there are no progress reports, but
1465 # the process is awoken immediately once the operation is complete.
1466 polling_interval = 15
1468 # Configuration option activation/auto_set_activation_skip.
1469 # Set the activation skip flag on new thin snapshot LVs.
1470 # The --setactivationskip option overrides this setting.
1471 # An LV can have a persistent 'activation skip' flag. The flag causes
1472 # the LV to be skipped during normal activation. The lvchange/vgchange
1473 # -K option is required to activate LVs that have the activation skip
1474 # flag set. When this setting is enabled, the activation skip flag is
1475 # set on new thin snapshot LVs.
1476 # This configuration option has an automatic default value.
1477 # auto_set_activation_skip = 1
1479 # Configuration option activation/activation_mode.
1480 # How LVs with missing devices are activated.
1481 # The --activationmode option overrides this setting.
1485 # Only allow activation of an LV if all of the Physical Volumes it
1486 # uses are present. Other PVs in the Volume Group may be missing.
1488 # Like complete, but additionally RAID LVs of segment type raid1,
1489 # raid4, raid5, radid6 and raid10 will be activated if there is no
1490 # data loss, i.e. they have sufficient redundancy to present the
1491 # entire addressable range of the Logical Volume.
1493 # Allows the activation of any LV even if a missing or failed PV
1494 # could cause data loss with a portion of the LV inaccessible.
1495 # This setting should not normally be used, but may sometimes
1496 # assist with data recovery.
1498 activation_mode = "degraded"
1500 # Configuration option activation/lock_start_list.
1501 # Locking is started only for VGs selected by this list.
1502 # The rules are the same as those for volume_list.
1503 # This configuration option does not have a default value defined.
1505 # Configuration option activation/auto_lock_start_list.
1506 # Locking is auto-started only for VGs selected by this list.
1507 # The rules are the same as those for auto_activation_volume_list.
1508 # This configuration option does not have a default value defined.
1511 # Configuration section metadata.
1512 # This configuration section has an automatic default value.
1515 # Configuration option metadata/check_pv_device_sizes.
1516 # Check device sizes are not smaller than corresponding PV sizes.
1517 # If device size is less than corresponding PV size found in metadata,
1518 # there is always a risk of data loss. If this option is set, then LVM
1519 # issues a warning message each time it finds that the device size is
1520 # less than corresponding PV size. You should not disable this unless
1521 # you are absolutely sure about what you are doing!
1522 # This configuration option is advanced.
1523 # This configuration option has an automatic default value.
1524 # check_pv_device_sizes = 1
1526 # Configuration option metadata/record_lvs_history.
1527 # When enabled, LVM keeps history records about removed LVs in
1528 # metadata. The information that is recorded in metadata for
1529 # historical LVs is reduced when compared to original
1530 # information kept in metadata for live LVs. Currently, this
1531 # feature is supported for thin and thin snapshot LVs only.
1532 # This configuration option has an automatic default value.
1533 # record_lvs_history = 0
1535 # Configuration option metadata/lvs_history_retention_time.
1536 # Retention time in seconds after which a record about individual
1537 # historical logical volume is automatically destroyed.
1538 # A value of 0 disables this feature.
1539 # This configuration option has an automatic default value.
1540 # lvs_history_retention_time = 0
1542 # Configuration option metadata/pvmetadatacopies.
1543 # Number of copies of metadata to store on each PV.
1544 # The --pvmetadatacopies option overrides this setting.
1548 # Two copies of the VG metadata are stored on the PV, one at the
1549 # front of the PV, and one at the end.
1551 # One copy of VG metadata is stored at the front of the PV.
1553 # No copies of VG metadata are stored on the PV. This may be
1554 # useful for VGs containing large numbers of PVs.
1556 # This configuration option is advanced.
1557 # This configuration option has an automatic default value.
1558 # pvmetadatacopies = 1
1560 # Configuration option metadata/vgmetadatacopies.
1561 # Number of copies of metadata to maintain for each VG.
1562 # The --vgmetadatacopies option overrides this setting.
1563 # If set to a non-zero value, LVM automatically chooses which of the
1564 # available metadata areas to use to achieve the requested number of
1565 # copies of the VG metadata. If you set a value larger than the the
1566 # total number of metadata areas available, then metadata is stored in
1567 # them all. The value 0 (unmanaged) disables this automatic management
1568 # and allows you to control which metadata areas are used at the
1569 # individual PV level using pvchange --metadataignore y|n.
1570 # This configuration option has an automatic default value.
1571 # vgmetadatacopies = 0
1573 # Configuration option metadata/pvmetadatasize.
1574 # Approximate number of sectors to use for each metadata copy.
1575 # VGs with large numbers of PVs or LVs, or VGs containing complex LV
1576 # structures, may need additional space for VG metadata. The metadata
1577 # areas are treated as circular buffers, so unused space becomes filled
1578 # with an archive of the most recent previous versions of the metadata.
1579 # This configuration option has an automatic default value.
1580 # pvmetadatasize = 255
1582 # Configuration option metadata/pvmetadataignore.
1583 # Ignore metadata areas on a new PV.
1584 # The --metadataignore option overrides this setting.
1585 # If metadata areas on a PV are ignored, LVM will not store metadata
1587 # This configuration option is advanced.
1588 # This configuration option has an automatic default value.
1589 # pvmetadataignore = 0
1591 # Configuration option metadata/stripesize.
1592 # This configuration option is advanced.
1593 # This configuration option has an automatic default value.
1596 # Configuration option metadata/dirs.
1597 # Directories holding live copies of text format metadata.
1598 # These directories must not be on logical volumes!
1599 # It's possible to use LVM with a couple of directories here,
1600 # preferably on different (non-LV) filesystems, and with no other
1601 # on-disk metadata (pvmetadatacopies = 0). Or this can be in addition
1602 # to on-disk metadata areas. The feature was originally added to
1603 # simplify testing and is not supported under low memory situations -
1604 # the machine could lock up. Never edit any files in these directories
1605 # by hand unless you are absolutely sure you know what you are doing!
1606 # Use the supplied toolset to make changes (e.g. vgcfgrestore).
1609 # dirs = [ "/etc/lvm/metadata", "/mnt/disk2/lvm/metadata2" ]
1611 # This configuration option is advanced.
1612 # This configuration option does not have a default value defined.
1615 # Configuration section report.
1616 # LVM report command output formatting.
1617 # This configuration section has an automatic default value.
1620 # Configuration option report/output_format.
1621 # Format of LVM command's report output.
1622 # If there is more than one report per command, then the format
1623 # is applied for all reports. You can also change output format
1624 # directly on command line using --reportformat option which
1625 # has precedence over log/output_format setting.
1628 # Original format with columns and rows. If there is more than
1629 # one report per command, each report is prefixed with report's
1630 # name for identification.
1633 # This configuration option has an automatic default value.
1634 # output_format = "basic"
1636 # Configuration option report/compact_output.
1637 # Do not print empty values for all report fields.
1638 # If enabled, all fields that don't have a value set for any of the
1639 # rows reported are skipped and not printed. Compact output is
1640 # applicable only if report/buffered is enabled. If you need to
1641 # compact only specified fields, use compact_output=0 and define
1642 # report/compact_output_cols configuration setting instead.
1643 # This configuration option has an automatic default value.
1644 # compact_output = 0
1646 # Configuration option report/compact_output_cols.
1647 # Do not print empty values for specified report fields.
1648 # If defined, specified fields that don't have a value set for any
1649 # of the rows reported are skipped and not printed. Compact output
1650 # is applicable only if report/buffered is enabled. If you need to
1651 # compact all fields, use compact_output=1 instead in which case
1652 # the compact_output_cols setting is then ignored.
1653 # This configuration option has an automatic default value.
1654 # compact_output_cols = ""
1656 # Configuration option report/aligned.
1657 # Align columns in report output.
1658 # This configuration option has an automatic default value.
1661 # Configuration option report/buffered.
1662 # Buffer report output.
1663 # When buffered reporting is used, the report's content is appended
1664 # incrementally to include each object being reported until the report
1665 # is flushed to output which normally happens at the end of command
1666 # execution. Otherwise, if buffering is not used, each object is
1667 # reported as soon as its processing is finished.
1668 # This configuration option has an automatic default value.
1671 # Configuration option report/headings.
1672 # Show headings for columns on report.
1673 # This configuration option has an automatic default value.
1676 # Configuration option report/separator.
1677 # A separator to use on report after each field.
1678 # This configuration option has an automatic default value.
1681 # Configuration option report/list_item_separator.
1682 # A separator to use for list items when reported.
1683 # This configuration option has an automatic default value.
1684 # list_item_separator = ","
1686 # Configuration option report/prefixes.
1687 # Use a field name prefix for each field reported.
1688 # This configuration option has an automatic default value.
1691 # Configuration option report/quoted.
1692 # Quote field values when using field name prefixes.
1693 # This configuration option has an automatic default value.
1696 # Configuration option report/columns_as_rows.
1697 # Output each column as a row.
1698 # If set, this also implies report/prefixes=1.
1699 # This configuration option has an automatic default value.
1700 # columns_as_rows = 0
1702 # Configuration option report/binary_values_as_numeric.
1703 # Use binary values 0 or 1 instead of descriptive literal values.
1704 # For columns that have exactly two valid values to report
1705 # (not counting the 'unknown' value which denotes that the
1706 # value could not be determined).
1707 # This configuration option has an automatic default value.
1708 # binary_values_as_numeric = 0
1710 # Configuration option report/time_format.
1711 # Set time format for fields reporting time values.
1712 # Format specification is a string which may contain special character
1713 # sequences and ordinary character sequences. Ordinary character
1714 # sequences are copied verbatim. Each special character sequence is
1715 # introduced by the '%' character and such sequence is then
1716 # substituted with a value as described below.
1720 # The abbreviated name of the day of the week according to the
1723 # The full name of the day of the week according to the current
1726 # The abbreviated month name according to the current locale.
1728 # The full month name according to the current locale.
1730 # The preferred date and time representation for the current
1733 # The century number (year/100) as a 2-digit integer. (alt E)
1735 # The day of the month as a decimal number (range 01 to 31).
1738 # Equivalent to %m/%d/%y. (For Americans only. Americans should
1739 # note that in other countries%d/%m/%y is rather common. This
1740 # means that in international context this format is ambiguous and
1741 # should not be used.
1743 # Like %d, the day of the month as a decimal number, but a leading
1744 # zero is replaced by a space. (alt O)
1746 # Modifier: use alternative local-dependent representation if
1749 # Equivalent to %Y-%m-%d (the ISO 8601 date format).
1751 # The ISO 8601 week-based year with century as adecimal number.
1752 # The 4-digit year corresponding to the ISO week number (see %V).
1753 # This has the same format and value as %Y, except that if the
1754 # ISO week number belongs to the previous or next year, that year
1757 # Like %G, but without century, that is, with a 2-digit year
1762 # The hour as a decimal number using a 24-hour clock
1763 # (range 00 to 23). (alt O)
1765 # The hour as a decimal number using a 12-hour clock
1766 # (range 01 to 12). (alt O)
1768 # The day of the year as a decimal number (range 001 to 366).
1770 # The hour (24-hour clock) as a decimal number (range 0 to 23);
1771 # single digits are preceded by a blank. (See also %H.)
1773 # The hour (12-hour clock) as a decimal number (range 1 to 12);
1774 # single digits are preceded by a blank. (See also %I.)
1776 # The month as a decimal number (range 01 to 12). (alt O)
1778 # The minute as a decimal number (range 00 to 59). (alt O)
1780 # Modifier: use alternative numeric symbols.
1782 # Either "AM" or "PM" according to the given time value,
1783 # or the corresponding strings for the current locale. Noon is
1784 # treated as "PM" and midnight as "AM".
1786 # Like %p but in lowercase: "am" or "pm" or a corresponding
1787 # string for the current locale.
1789 # The time in a.m. or p.m. notation. In the POSIX locale this is
1790 # equivalent to %I:%M:%S %p.
1792 # The time in 24-hour notation (%H:%M). For a version including
1793 # the seconds, see %T below.
1795 # The number of seconds since the Epoch,
1796 # 1970-01-01 00:00:00 +0000 (UTC)
1798 # The second as a decimal number (range 00 to 60). (The range is
1799 # up to 60 to allow for occasional leap seconds.) (alt O)
1803 # The time in 24-hour notation (%H:%M:%S).
1805 # The day of the week as a decimal, range 1 to 7, Monday being 1.
1806 # See also %w. (alt O)
1808 # The week number of the current year as a decimal number,
1809 # range 00 to 53, starting with the first Sunday as the first
1810 # day of week 01. See also %V and %W. (alt O)
1812 # The ISO 8601 week number of the current year as a decimal number,
1813 # range 01 to 53, where week 1 is the first week that has at least
1814 # 4 days in the new year. See also %U and %W. (alt O)
1816 # The day of the week as a decimal, range 0 to 6, Sunday being 0.
1817 # See also %u. (alt O)
1819 # The week number of the current year as a decimal number,
1820 # range 00 to 53, starting with the first Monday as the first day
1821 # of week 01. (alt O)
1823 # The preferred date representation for the current locale without
1826 # The preferred time representation for the current locale without
1829 # The year as a decimal number without a century (range 00 to 99).
1832 # The year as a decimal number including the century. (alt E)
1834 # The +hhmm or -hhmm numeric timezone (that is, the hour and minute
1837 # The timezone name or abbreviation.
1839 # A literal '%' character.
1841 # This configuration option has an automatic default value.
1842 # time_format = "%Y-%m-%d %T %z"
1844 # Configuration option report/devtypes_sort.
1845 # List of columns to sort by when reporting 'lvm devtypes' command.
1846 # See 'lvm devtypes -o help' for the list of possible fields.
1847 # This configuration option has an automatic default value.
1848 # devtypes_sort = "devtype_name"
1850 # Configuration option report/devtypes_cols.
1851 # List of columns to report for 'lvm devtypes' command.
1852 # See 'lvm devtypes -o help' for the list of possible fields.
1853 # This configuration option has an automatic default value.
1854 # devtypes_cols = "devtype_name,devtype_max_partitions,devtype_description"
1856 # Configuration option report/devtypes_cols_verbose.
1857 # List of columns to report for 'lvm devtypes' command in verbose mode.
1858 # See 'lvm devtypes -o help' for the list of possible fields.
1859 # This configuration option has an automatic default value.
1860 # devtypes_cols_verbose = "devtype_name,devtype_max_partitions,devtype_description"
1862 # Configuration option report/lvs_sort.
1863 # List of columns to sort by when reporting 'lvs' command.
1864 # See 'lvs -o help' for the list of possible fields.
1865 # This configuration option has an automatic default value.
1866 # lvs_sort = "vg_name,lv_name"
1868 # Configuration option report/lvs_cols.
1869 # List of columns to report for 'lvs' command.
1870 # See 'lvs -o help' for the list of possible fields.
1871 # This configuration option has an automatic default value.
1872 # 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"
1874 # Configuration option report/lvs_cols_verbose.
1875 # List of columns to report for 'lvs' command in verbose mode.
1876 # See 'lvs -o help' for the list of possible fields.
1877 # This configuration option has an automatic default value.
1878 # 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"
1880 # Configuration option report/vgs_sort.
1881 # List of columns to sort by when reporting 'vgs' command.
1882 # See 'vgs -o help' for the list of possible fields.
1883 # This configuration option has an automatic default value.
1884 # vgs_sort = "vg_name"
1886 # Configuration option report/vgs_cols.
1887 # List of columns to report for 'vgs' command.
1888 # See 'vgs -o help' for the list of possible fields.
1889 # This configuration option has an automatic default value.
1890 # vgs_cols = "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
1892 # Configuration option report/vgs_cols_verbose.
1893 # List of columns to report for 'vgs' command in verbose mode.
1894 # See 'vgs -o help' for the list of possible fields.
1895 # This configuration option has an automatic default value.
1896 # vgs_cols_verbose = "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
1898 # Configuration option report/pvs_sort.
1899 # List of columns to sort by when reporting 'pvs' command.
1900 # See 'pvs -o help' for the list of possible fields.
1901 # This configuration option has an automatic default value.
1902 # pvs_sort = "pv_name"
1904 # Configuration option report/pvs_cols.
1905 # List of columns to report for 'pvs' command.
1906 # See 'pvs -o help' for the list of possible fields.
1907 # This configuration option has an automatic default value.
1908 # pvs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
1910 # Configuration option report/pvs_cols_verbose.
1911 # List of columns to report for 'pvs' command in verbose mode.
1912 # See 'pvs -o help' for the list of possible fields.
1913 # This configuration option has an automatic default value.
1914 # pvs_cols_verbose = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
1916 # Configuration option report/segs_sort.
1917 # List of columns to sort by when reporting 'lvs --segments' command.
1918 # See 'lvs --segments -o help' for the list of possible fields.
1919 # This configuration option has an automatic default value.
1920 # segs_sort = "vg_name,lv_name,seg_start"
1922 # Configuration option report/segs_cols.
1923 # List of columns to report for 'lvs --segments' command.
1924 # See 'lvs --segments -o help' for the list of possible fields.
1925 # This configuration option has an automatic default value.
1926 # segs_cols = "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
1928 # Configuration option report/segs_cols_verbose.
1929 # List of columns to report for 'lvs --segments' command in verbose mode.
1930 # See 'lvs --segments -o help' for the list of possible fields.
1931 # This configuration option has an automatic default value.
1932 # segs_cols_verbose = "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
1934 # Configuration option report/pvsegs_sort.
1935 # List of columns to sort by when reporting 'pvs --segments' command.
1936 # See 'pvs --segments -o help' for the list of possible fields.
1937 # This configuration option has an automatic default value.
1938 # pvsegs_sort = "pv_name,pvseg_start"
1940 # Configuration option report/pvsegs_cols.
1941 # List of columns to sort by when reporting 'pvs --segments' command.
1942 # See 'pvs --segments -o help' for the list of possible fields.
1943 # This configuration option has an automatic default value.
1944 # pvsegs_cols = "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
1946 # Configuration option report/pvsegs_cols_verbose.
1947 # List of columns to sort by when reporting 'pvs --segments' command in verbose mode.
1948 # See 'pvs --segments -o help' for the list of possible fields.
1949 # This configuration option has an automatic default value.
1950 # 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"
1952 # Configuration option report/vgs_cols_full.
1953 # List of columns to report for lvm fullreport's 'vgs' subreport.
1954 # See 'vgs -o help' for the list of possible fields.
1955 # This configuration option has an automatic default value.
1956 # vgs_cols_full = "vg_all"
1958 # Configuration option report/pvs_cols_full.
1959 # List of columns to report for lvm fullreport's 'vgs' subreport.
1960 # See 'pvs -o help' for the list of possible fields.
1961 # This configuration option has an automatic default value.
1962 # pvs_cols_full = "pv_all"
1964 # Configuration option report/lvs_cols_full.
1965 # List of columns to report for lvm fullreport's 'lvs' subreport.
1966 # See 'lvs -o help' for the list of possible fields.
1967 # This configuration option has an automatic default value.
1968 # lvs_cols_full = "lv_all"
1970 # Configuration option report/pvsegs_cols_full.
1971 # List of columns to report for lvm fullreport's 'pvseg' subreport.
1972 # See 'pvs --segments -o help' for the list of possible fields.
1973 # This configuration option has an automatic default value.
1974 # pvsegs_cols_full = "pvseg_all,pv_uuid,lv_uuid"
1976 # Configuration option report/segs_cols_full.
1977 # List of columns to report for lvm fullreport's 'seg' subreport.
1978 # See 'lvs --segments -o help' for the list of possible fields.
1979 # This configuration option has an automatic default value.
1980 # segs_cols_full = "seg_all,lv_uuid"
1982 # Configuration option report/vgs_sort_full.
1983 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
1984 # See 'vgs -o help' for the list of possible fields.
1985 # This configuration option has an automatic default value.
1986 # vgs_sort_full = "vg_name"
1988 # Configuration option report/pvs_sort_full.
1989 # List of columns to sort by when reporting lvm fullreport's 'vgs' subreport.
1990 # See 'pvs -o help' for the list of possible fields.
1991 # This configuration option has an automatic default value.
1992 # pvs_sort_full = "pv_name"
1994 # Configuration option report/lvs_sort_full.
1995 # List of columns to sort by when reporting lvm fullreport's 'lvs' subreport.
1996 # See 'lvs -o help' for the list of possible fields.
1997 # This configuration option has an automatic default value.
1998 # lvs_sort_full = "vg_name,lv_name"
2000 # Configuration option report/pvsegs_sort_full.
2001 # List of columns to sort by when reporting for lvm fullreport's 'pvseg' subreport.
2002 # See 'pvs --segments -o help' for the list of possible fields.
2003 # This configuration option has an automatic default value.
2004 # pvsegs_sort_full = "pv_uuid,pvseg_start"
2006 # Configuration option report/segs_sort_full.
2007 # List of columns to sort by when reporting lvm fullreport's 'seg' subreport.
2008 # See 'lvs --segments -o help' for the list of possible fields.
2009 # This configuration option has an automatic default value.
2010 # segs_sort_full = "lv_uuid,seg_start"
2012 # Configuration option report/mark_hidden_devices.
2013 # Use brackets [] to mark hidden devices.
2014 # This configuration option has an automatic default value.
2015 # mark_hidden_devices = 1
2017 # Configuration option report/two_word_unknown_device.
2018 # Use the two words 'unknown device' in place of '[unknown]'.
2019 # This is displayed when the device for a PV is not known.
2020 # This configuration option has an automatic default value.
2021 # two_word_unknown_device = 0
2024 # Configuration section dmeventd.
2025 # Settings for the LVM event daemon.
2028 # Configuration option dmeventd/mirror_library.
2029 # The library dmeventd uses when monitoring a mirror device.
2030 # libdevmapper-event-lvm2mirror.so attempts to recover from
2031 # failures. It removes failed devices from a volume group and
2032 # reconfigures a mirror as necessary. If no mirror library is
2033 # provided, mirrors are not monitored through dmeventd.
2034 mirror_library = "libdevmapper-event-lvm2mirror.so"
2036 # Configuration option dmeventd/raid_library.
2037 # This configuration option has an automatic default value.
2038 # raid_library = "libdevmapper-event-lvm2raid.so"
2040 # Configuration option dmeventd/snapshot_library.
2041 # The library dmeventd uses when monitoring a snapshot device.
2042 # libdevmapper-event-lvm2snapshot.so monitors the filling of snapshots
2043 # and emits a warning through syslog when the usage exceeds 80%. The
2044 # warning is repeated when 85%, 90% and 95% of the snapshot is filled.
2045 snapshot_library = "libdevmapper-event-lvm2snapshot.so"
2047 # Configuration option dmeventd/thin_library.
2048 # The library dmeventd uses when monitoring a thin device.
2049 # libdevmapper-event-lvm2thin.so monitors the filling of a pool
2050 # and emits a warning through syslog when the usage exceeds 80%. The
2051 # warning is repeated when 85%, 90% and 95% of the pool is filled.
2052 thin_library = "libdevmapper-event-lvm2thin.so"
2054 # Configuration option dmeventd/executable.
2055 # The full path to the dmeventd binary.
2056 # This configuration option has an automatic default value.
2057 # executable = "/sbin/dmeventd"
2060 # Configuration section tags.
2061 # Host tag settings.
2062 # This configuration section has an automatic default value.
2065 # Configuration option tags/hosttags.
2066 # Create a host tag using the machine name.
2067 # The machine name is nodename returned by uname(2).
2068 # This configuration option has an automatic default value.
2071 # Configuration section tags/<tag>.
2072 # Replace this subsection name with a custom tag name.
2073 # Multiple subsections like this can be created. The '@' prefix for
2074 # tags is optional. This subsection can contain host_list, which is a
2075 # list of machine names. If the name of the local machine is found in
2076 # host_list, then the name of this subsection is used as a tag and is
2077 # applied to the local machine as a 'host tag'. If this subsection is
2078 # empty (has no host_list), then the subsection name is always applied
2082 # The host tag foo is given to all hosts, and the host tag
2083 # bar is given to the hosts named machine1 and machine2.
2084 # tags { foo { } bar { host_list = [ "machine1", "machine2" ] } }
2086 # This configuration section has variable name.
2087 # This configuration section has an automatic default value.
2090 # Configuration option tags/<tag>/host_list.
2091 # A list of machine names.
2092 # These machine names are compared to the nodename returned
2093 # by uname(2). If the local machine name matches an entry in
2094 # this list, the name of the subsection is applied to the
2095 # machine as a 'host tag'.
2096 # This configuration option does not have a default value defined.