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