shaba/lvm2
1
0
Fork 0
mirror of git://sourceware.org/git/lvm2.git synced 2024-12-30 17:18:21 +03:00
Code Releases Activity
ca38251b10
lvm2/lib/config/defaults.h

333 lines
13 KiB
C
Raw Normal View History

o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
/*
Add defines for default vgcreate parameters.
2009-07-09 14:00:36 +04:00
* Copyright (C) 2001-2004 Sistina Software, Inc. All rights reserved.
sparse: configurable type for sparse volumes Support compile type configurable defaults for creation of sparse volumes. By default now create 'thin-pools' for sparse volumes. Use the global/sparse_segtype_default to switch back to old snapshots if needed. Apply the same compile logic for newly introduces mirror/raid1 options.
2014-10-31 01:38:02 +03:00
* Copyright (C) 2004-2014 Red Hat, Inc. All rights reserved.
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
*
Update copyright notices.
2004-03-30 23:35:44 +04:00
* This file is part of LVM2.
*
* This copyrighted material is made available to anyone wishing to use,
* modify, copy, or redistribute it subject to the terms and conditions
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* of the GNU Lesser General Public License v.2.1.
Update copyright notices.
2004-03-30 23:35:44 +04:00
*
Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.
2007-08-21 00:55:30 +04:00
* You should have received a copy of the GNU Lesser General Public License
Update copyright notices.
2004-03-30 23:35:44 +04:00
* along with this program; if not, write to the Free Software Foundation,
doc: change fsf address Hmm rpmlint suggest fsf is using a different address these days, so lets keep it up-to-date
2016-01-21 13:49:46 +03:00
* Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
*/
#ifndef _LVM_DEFAULTS_H
#define _LVM_DEFAULTS_H
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
#include "device_mapper/vdo/vdo_limits.h"
Place the first PE at 1 MiB for all defaults . When using default settings, this commit should change nothing. The first PE continues to be placed at 1 MiB resulting in a metadata area size of 1020 KiB (for 4K page sizes; slightly smaller for larger page sizes.) . When default_data_alignment is disabled in lvm.conf, align pe_start at 1 MiB, based on a default metadata area size that adapts to the page size. Previously, disabling this option would result in mda_size that was too small for common use, and produced a 64 KiB aligned pe_start. . Customized pe_start and mda_size values continue to be set as before in lvm.conf and command line. . Remove the configure option for setting default_data_alignment at build time. . Improve alignment related option descriptions. . Add section about alignment to pvcreate man page. Previously, DEFAULT_PVMETADATASIZE was 255 sectors. However, the fact that the config setting named "default_data_alignment" has a default value of 1 (MiB) meant that DEFAULT_PVMETADATASIZE was having no effect. The metadata area size is the space between the start of the metadata area (page size offset from the start of the device) and the first PE (1 MiB by default due to default_data_alignment 1.) The result is a 1020 KiB metadata area on machines with 4KiB page size (1024 KiB - 4 KiB), and smaller on machines with larger page size. If default_data_alignment was set to 0 (disabled), then DEFAULT_PVMETADATASIZE 255 would take effect, and produce a metadata area that was 188 KiB and pe_start of 192 KiB. This was too small for common use. This is fixed by making the default metadata area size a computed value that matches the value produced by default_data_alignment.
2018-11-14 00:00:11 +03:00
/*
* By default the first PE is placed at 1 MiB.
*
* If default_data_alignment is 2, then the first PE
* is placed at 2 * 1 MiB.
*
* If default_data_alignment is 3, then the first PE
* is placed at 3 * 1 MiB.
*/
#define FIRST_PE_AT_ONE_MB_IN_SECTORS 2048 /* 1 MiB in 512 byte sectors */
#define FIRST_PE_AT_ONE_MB_IN_MB 1
Change default alignment of pe_start to 1MB. The new standard in the storage industry is to default alignment of data areas to 1MB. fdisk, parted, and mdadm have all been updated to this default. Update LVM to align the PV's data area start (pe_start) to 1MB. This provides a more useful default than the previous default of 64K (which generally ended up being a 192K pe_start once the first metadata area was created). Before this patch: # pvs -o name,vg_mda_size,pe_start PV VMdaSize 1st PE /dev/sdd 188.00k 192.00k After this patch: # pvs -o name,vg_mda_size,pe_start PV VMdaSize 1st PE /dev/sdd 1020.00k 1.00m The heuristic for setting the default alignment for LVM data areas is: - If the default value (1MB) is a multiple of the detected alignment then just use the default. - Otherwise, use the detected value. In practice this means we'll almost always use 1MB -- that is unless: - the alignment was explicitly specified with --dataalignment - or MD's full stripe width, or the {minimum,optimal}_io_size exceeds 1MB - or the specified/detected value is not a power-of-2
2010-08-12 08:11:48 +04:00
Another attempt to support both readline versions.
2002-01-08 22:17:08 +03:00
#define DEFAULT_ARCHIVE_ENABLED 1
#define DEFAULT_BACKUP_ENABLED 1
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
Move .cache file into a new /etc/lvm/cache directory by default. Add devices/cache_dir & devices/cache_file_prefix, deprecating devices/cache. Create directory in fcntl_lock_file() if required.
2007-02-28 21:27:13 +03:00
#define DEFAULT_CACHE_FILE_PREFIX ""
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
Another attempt to support both readline versions.
2002-01-08 22:17:08 +03:00
#define DEFAULT_ARCHIVE_DAYS 30
#define DEFAULT_ARCHIVE_NUMBER 10
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
#define DEFAULT_DEV_DIR "/dev"
o More comprehensive config parameter debugging messages. o Make /proc configurable. o Review hard-coded "/dev"s - made 2 more of them configurable.
2002-01-16 02:34:13 +03:00
#define DEFAULT_PROC_DIR "/proc"
config: Adjust system_id defaults. Allow cmd->unknown_system_id to be cleared during toolcontext refresh. Set a default value of "none" for global/system_id_source. Allow local/system_id to be empty so it's not impossible for a later config file to remove it.
2015-02-24 00:20:51 +03:00
#define DEFAULT_SYSTEM_ID_SOURCE "none"
devices: rework libudev usage related to config settings: obtain_device_info_from_udev (controls if lvm gets a list of devices from readdir /dev or from libudev) external_device_info_source (controls if lvm asks libudev for device information) . Make the obtain_device_list_from_udev setting affect only the choice of readdir /dev vs libudev. The setting no longer controls if udev is used for device type checks. . Change obtain_device_list_from_udev default to 0. This helps avoid boot timeouts due to slow libudev queries, avoids reported failures from udev_enumerate_scan_devices, and avoids delays from "device not initialized in udev database" errors. Even without errors, for a system booting with 1024 PVs, lvm2-pvscan times improve from about 100 sec to 15 sec, and the pvscan command from about 64 sec to about 4 sec. . For external_device_info_source="none", remove all libudev device info queries, and use only lvm native device info. . For external_device_info_source="udev", first check lvm native device info, then check libudev info. . Remove sleep/retry loop when attempting libudev queries for device info. udev info will simply be skipped if it's not immediately available. . Only set up a libdev connection if it will be used by obtain_device_list_from_udev/external_device_info_source. . For native multipath component detection, use /etc/multipath/wwids. If a device has a wwid matching an entry in the wwids file, then it's considered a multipath component. This is necessary to natively detect multipath components when the mpath device is not set up.
2021-06-09 01:12:09 +03:00
#define DEFAULT_OBTAIN_DEVICE_LIST_FROM_UDEV 0
conf: add devices/external_device_info_source to lvm.conf
2014-12-15 18:27:33 +03:00
#define DEFAULT_EXTERNAL_DEVICE_INFO_SOURCE "none"
Sysfs block device filtering option for 2.6.
2004-02-13 17:46:04 +03:00
#define DEFAULT_SYSFS_SCAN 1
Set devices/md_component_detection = 1 to ignore devices containing md superblocks. [Luca Berra]
2004-04-16 20:12:04 +04:00
#define DEFAULT_MD_COMPONENT_DETECTION 1
filters: add firmware RAID filter Just like MD filtering that detects components of software RAID (md), add detection for firmware RAID. We're not adding any native code to detect this - there are lots of firmware RAIDs out there which is just out of LVM scope. However, with current changes with which we're able to get device info from external sources (e.g. external_device_info_source="udev"), we can do this easily if the external device status source has this kind of information - which is the case of "udev" source where the results of blkid scans are stored. This detection should cover all firmware RAIDs that blkid can detect and which are identified as: ID_FS_TYPE = {adaptec,ddf,hpt45x,hpt37x,isw,jmicron,lsi_mega,nvidia,promise_fasttrack,silicon_medley,via}_raid_member
2014-09-09 17:05:57 +04:00
#define DEFAULT_FW_RAID_COMPONENT_DETECTION 0
Add device/md_chunk_alignment to lvm.conf
2008-09-19 09:33:37 +04:00
#define DEFAULT_MD_CHUNK_ALIGNMENT 1
Mirror: Fix hangs and lock-ups caused by attempting label reads of mirrors There is a problem with the way mirrors have been designed to handle failures that is resulting in stuck LVM processes and hung I/O. When mirrors encounter a write failure, they block I/O and notify userspace to reconfigure the mirror to remove failed devices. This process is open to a couple races: 1) Any LVM process other than the one that is meant to deal with the mirror failure can attempt to read the mirror, fail, and block other LVM commands (including the repair command) from proceeding due to holding a lock on the volume group. 2) If there are multiple mirrors that suffer a failure in the same volume group, a repair can block while attempting to read the LVM label from one mirror while trying to repair the other. Mitigation of these races has been attempted by disallowing label reading of mirrors that are either suspended or are indicated as blocking by the kernel. While this has closed the window of opportunity for hitting the above problems considerably, it hasn't closed it completely. This is because it is still possible to start an LVM command, read the status of the mirror as healthy, and then perform the read for the label at the moment after a the failure is discovered by the kernel. I can see two solutions to this problem: 1) Allow users to configure whether mirrors can be candidates for LVM labels (i.e. whether PVs can be created on mirror LVs). If the user chooses to allow label scanning of mirror LVs, it will be at the expense of a possible hang in I/O or LVM processes. 2) Instrument a way to allow asynchronous label reading - allowing blocked label reads to be ignored while continuing to process the LVM command. This would action would allow LVM commands to continue even though they would have otherwise blocked trying to read a mirror. They can then release their lock and allow a repair command to commence. In the event of #2 above, the repair command already in progress can continue and repair the failed mirror. This patch brings solution #1. If solution #2 is developed later on, the configuration option created in #1 can be negated - allowing mirrors to be scanned for labels by default once again.
2013-10-23 04:14:33 +04:00
#define DEFAULT_IGNORE_LVM_MIRRORS 1
Do not scan device if it is part of active multipath. Add filter which tries to check if scanned device is part of active multipath. Firstly, only SCSI major number devices are handled in filter. Then it checks if device has exactly one holder (in sysfs) and if it is device-mapper device and DM-UUID is prefixed by "MPATH-". If so, this device is filtered out. The whole filter can be switched off by setting mpath_component_detection in lvm.conf. https://bugzilla.redhat.com/show_bug.cgi?id=597010 Signed-off-by: Milan Broz <mbroz@redhat.com>
2011-11-11 19:11:08 +04:00
#define DEFAULT_MULTIPATH_COMPONENT_DETECTION 1
config: use devices/ignore_suspended_devices=0 by default ignore_suspended_devices=0 is already used in lvm.conf we distribute, but it was still "1" in the code (so it was used when lvm.conf value was not defined). It should be "0" too.
2014-04-24 14:12:28 +04:00
#define DEFAULT_IGNORE_SUSPENDED_DEVICES 0
Require --restorefile when using pvcreate --uuid. Introduce --norestorefile to allow user to override the new requirement. This can also be overridden with "devices/require_restorefile_with_uuid" in lvm.conf -- however the default is 1. Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2010-08-12 08:08:59 +04:00
#define DEFAULT_REQUIRE_RESTOREFILE_WITH_UUID 1
Add devices/data_alignment_offset_detection to lvm.conf. If the pvcreate --dataalignmentoffset option is not specified the start of a PV's aligned data area will be shifted by the associated 'alignment_offset' exposed in sysfs (unless devices/data_alignment_offset_detection is disabled in lvm.conf). Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2009-08-01 21:07:36 +04:00
#define DEFAULT_DATA_ALIGNMENT_OFFSET_DETECTION 1
Add devices/data_alignment_detection to lvm.conf. Adds 'data_alignment_detection' config option to the devices section of lvm.conf. If your kernel provides topology information in sysfs (linux >= 2.6.31) for the Physical Volume, the start of data area will be aligned on a multiple of the ’minimum_io_size’ or ’optimal_io_size’ exposed in sysfs. minimum_io_size is used if optimal_io_size is undefined (0). If both md_chunk_alignment and data_alignment_detection are enabled the result of data_alignment_detection is used. Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2009-08-01 21:08:43 +04:00
#define DEFAULT_DATA_ALIGNMENT_DETECTION 1
Add "devices/issue_discards" to lvm.conf. Issue discards on lvremove if enabled and both storage and kernel have support.
2011-04-13 01:59:01 +04:00
#define DEFAULT_ISSUE_DISCARDS 0
Set pv_min_size to 2048KB to exclude floppy drives. Previously was 512.
2011-04-28 21:33:34 +04:00
#define DEFAULT_PV_MIN_SIZE_KB 2048
lvmcache: improve duplicate PV handling Wait to compare and choose alternate duplicate devices until after all devices are scanned. During scanning, the first duplicate dev is kept in lvmcache, and others are kept in a new list (_found_duplicate_devs). After all devices are scanned, compare all the duplicates available for a given PVID and decide which is best. If the dev used in lvmcache is changed, drop the old dev from lvmcache entirely and rescan the replacement dev. Previously the VG metadata from the old dev was kept in lvmcache and only the dev was replaced. A new config setting devices/allow_changes_with_duplicate_pvs can be set to 0 which disallows modifying a VG or activating LVs in it when the VG contains PVs with duplicate devices. Set to 1 is the old behavior which allowed the VG to be changed. The logic for which of two devs is preferred has changed. The primary goal is to choose a device that is currently in use if the other isn't, e.g. by an active LV. . prefer dev with fs mounted if the other doesn't, else . prefer dev that is dm if the other isn't, else . prefer dev in subsystem if the other isn't If neither device is preferred by these rules, then don't change devices in lvmcache, leaving the one that was found first. The previous logic for preferring a device was: . prefer dev in subsystem if the other isn't, else . prefer dev without holders if the other has holders, else . prefer dev that is dm if the other isn't
2016-02-09 22:06:27 +03:00
#define DEFAULT_ALLOW_CHANGES_WITH_DUPLICATE_PVS 0
o sync tool changes for backup stuff.
2002-01-07 14:12:11 +03:00
Change default locking_lib to liblvm2clusterlock.so.
2006-09-01 00:56:33 +04:00
#define DEFAULT_LOCKING_LIB "liblvm2clusterlock.so"
thin: errrorwhenfull support Support error_if_no_space feature for thin pools. Report more info about thinpool status: (out_of_data (D), metadata_read_only (M), failed (F) also as health attribute.)
2015-01-13 17:23:03 +03:00
#define DEFAULT_ERROR_WHEN_FULL 0
When using local file locking, skip clustered VGs. Add fallback_to_clustered_locking and fallback_to_local_locking parameters.
2006-09-02 05:18:17 +04:00
#define DEFAULT_FALLBACK_TO_LOCAL_LOCKING 1
#define DEFAULT_FALLBACK_TO_CLUSTERED_LOCKING 1
Add global/wait_for_locks to lvm.conf so blocking on locks can be disabled.
2009-07-25 03:28:55 +04:00
#define DEFAULT_WAIT_FOR_LOCKS 1
config: rename lock_retries lvmlockd_lock_retries Because it only applies to lvmlockd requests, but sounded too general.
2015-07-06 19:19:17 +03:00
#define DEFAULT_LVMLOCKD_LOCK_RETRIES 3
lvmetad: preemptively check and rescan in commands Move checking the lvmetad state, and the possible rescan, out of lvmetad_send() to the start of the command. Previously, the token mismatch and rescan would occur within lvmetad_send() for some other request. Now, the token mismatch is detected earlier, so the rescan can be done before the main command is in progress. Rescanning deep within the processing of another command will disturb the lvmcache state of that other command. A rescan already exists at the start of the command for the case where foreign VGs are going to be read. This same rescan is now also performed when there is an lvmetad token mismatch (from a changed global_filter). The commands pvscan/vgscan/lvscan/vgimport are excluded from this preemptive checking/rescanning for lvmetad because they want to do rescanning themselves explicitly. If rescanning devices fails, then lvmetad has not been correctly repopulated and should not be used, so make the command revert to not using lvmetad.
2016-01-29 01:40:26 +03:00
#define DEFAULT_LVMETAD_UPDATE_WAIT_TIME 10
Implement write lock prioritisation for file locking and make it default.
2009-09-02 18:47:39 +04:00
#define DEFAULT_PRIORITISE_WRITE_LOCKS 1
mlockall() -> mlock() This patch adds a new implementation of locking function instead of mlockall() that may lock way too much memory (>100MB). New function instead uses mlock() system call and selectively locks memory areas from /proc/self/maps trying to avoid locking areas unused during lock-ed state. Patch also adds struct cmd_context to all memlock() calls to have access to configuration. For backward compatibility functionality of mlockall() is preserved with "activation/use_mlockall" flag. As a simple check, locking and unlocking counts the amount of memory and compares whether values are matching.
2010-03-05 17:48:33 +03:00
#define DEFAULT_USE_MLOCKALL 0
Add global/metadata_read_only to use unrepaired metadata in read-only cmds.
2010-10-25 15:20:54 +04:00
#define DEFAULT_METADATA_READ_ONLY 0
pre-release
2012-01-26 18:02:42 +04:00
#define DEFAULT_LVDISPLAY_SHOWS_FULL_DEVICE_PATH 0
pvs: replace 'unknown device' with [unknown] A config setting can restore the old string.
2016-02-29 22:38:31 +03:00
#define DEFAULT_UNKNOWN_DEVICE_NAME "[unknown]"
io: use sync io if aio fails io_setup() for aio may fail if a system has reached the aio request limit. In this case, fall back to using sync io. Also, lvm use of aio can be disabled entirely with config setting global/use_aio=0. The system limit for aio requests can be seen from /proc/sys/fs/aio-max-nr The current usage of aio requests can be seen from /proc/sys/fs/aio-nr The system limit for aio requests can be increased by setting fs.aio-max-nr using sysctl. Also add last-byte limit to the sync io code.
2018-11-16 21:21:20 +03:00
#define DEFAULT_USE_AIO 1
move defaults.h
2002-02-08 17:28:52 +03:00
Add lvmlockd
2015-03-05 23:00:44 +03:00
#define DEFAULT_SANLOCK_LV_EXTEND_MB 256
mirror: extra parsing for mirrorlog arg Put validation of mirrorlog arg into a separate function.
2014-10-22 23:02:29 +04:00
#define DEFAULT_MIRRORLOG MIRROR_LOG_DISK
Add mirror log fault-handling policy.
2006-05-11 23:45:53 +04:00
#define DEFAULT_MIRROR_LOG_FAULT_POLICY "allocate"
Rename mirror_device_fault_policy to mirror_image_fault policy
2010-01-06 16:27:06 +03:00
#define DEFAULT_MIRROR_IMAGE_FAULT_POLICY "remove"
Do not allow creating mirrors of more than 8 images. This is kernel limitation in all kernel versions, so better detect this early.
2009-11-27 17:35:38 +03:00
#define DEFAULT_MIRROR_MAX_IMAGES 8 /* limited by kernel DM_KCOPYD_MAX_REGIONS */
lvcreate/lvconvert: fix validation of maximum mirrors/stripes Enforce mirror/raid0/1/10/4/5/6 type specific maximum images when creating LVs or converting them from mirror <-> raid1. Document those maxima in the lvcreate/lvconvert man pages. - resolves rhbz1366060
2016-08-12 20:14:28 +03:00
/* Limited by kernel failed devices bitfield in superblock (raid4/5/6 MD max 253) */
/*
* FIXME: Increase these to 64 and further to the MD maximum
* once the SubLVs split and name shift got enhanced
*/
lvconvert/lvcreate: raise maximum number of raid images Because of contraints in renaming shifted rimage/rmeta LV names the current RaidLV limit is a maximum of 10 SubLV pairs. With the previous introduction of reshaping infratructure that constriant got removed. Kernel supports 253 since dm-raid target 1.9.0, older kernels 64. Raise the maximum number of RaidLV rimage/rmeta pairs to 64. If we want to raise past 64, we have to introdce a check for the kernel supporting it in lvcreate/lvconvert. Related: rhbz834579 Related: rhbz1191935 Related: rhbz1191978
2017-02-24 06:41:46 +03:00
#define DEFAULT_RAID1_MAX_IMAGES 64
#define DEFAULT_RAID_MAX_IMAGES 64
lvcreate: raid0 needs default number of stripes Commit 3928c96a37941d765bf467d82502cd2aec7fd809 introduced new defaults for raid number of stripes, which may cause backwards compatibility issues with customer scripts. Adding configurable option 'raid_stripe_all_devices' defaulting to '0' (i.e. off = new behaviour) to select the old behaviour of using all PVs in the VG or those provided on the command line. In case any scripts rely on the old behaviour, just set 'raid_strip_all_devices = 1'. - resolves rhbz1354650
2016-07-20 18:20:15 +03:00
#define DEFAULT_ALLOCATION_STRIPE_ALL_DEVICES 0 /* Don't stripe across all devices if not -i/--stripes given */
raid: Introduce DEFAULT_RAID_MAX_IMAGES Prepare to allow for the number of images in a raid set to be larger than the limit for old-style dm raid1.
2015-09-28 23:38:40 +03:00
Add policy based automated repair of RAID logical volumes The RAID plug-in for dmeventd now calls 'lvconvert --repair' to address failures of devices in a RAID logical volume. The action taken can be either to "warn" or "allocate" a new device from any spares that may be available in the volume group. The action is designated by setting 'raid_fault_policy' in lvm.conf - the default being "warn".
2011-12-06 23:30:15 +04:00
#define DEFAULT_RAID_FAULT_POLICY "warn"
sparse: configurable type for sparse volumes Support compile type configurable defaults for creation of sparse volumes. By default now create 'thin-pools' for sparse volumes. Use the global/sparse_segtype_default to switch back to old snapshots if needed. Apply the same compile logic for newly introduces mirror/raid1 options.
2014-10-31 01:38:02 +03:00
Add dmeventd monitoring for RAID devices.
2011-08-11 09:00:20 +04:00
#define DEFAULT_DMEVENTD_RAID_LIB "libdevmapper-event-lvm2raid.so"
Add config file setting: dmeventd/mirror_library
2006-01-27 22:05:05 +03:00
#define DEFAULT_DMEVENTD_MIRROR_LIB "libdevmapper-event-lvm2mirror.so"
Various small cleanups and fixes related to monitoring.
2010-08-17 02:54:35 +04:00
#define DEFAULT_DMEVENTD_SNAPSHOT_LIB "libdevmapper-event-lvm2snapshot.so"
Thin add dmeventd support This is basic version with still few unresolved issue mainly in case, when the pool resize is failing.
2011-12-21 17:08:11 +04:00
#define DEFAULT_DMEVENTD_THIN_LIB "libdevmapper-event-lvm2thin.so"
config: new option dmeventd/thin_command This setting will allowing configuring which command gets executed when thin-pool fullness goes from 50%..100%
2017-01-18 11:54:32 +03:00
#define DEFAULT_DMEVENTD_THIN_COMMAND "lvm lvextend --use-policies"
dmeventd: lvm vdo support
2018-07-09 12:43:12 +03:00
#define DEFAULT_DMEVENTD_VDO_LIB "libdevmapper-event-lvm2vdo.so"
#define DEFAULT_DMEVENTD_VDO_COMMAND "lvm lvextend --use-policies"
Add --monitor to vgcreate and lvcreate to control dmeventd registration. Propagate --monitor around cluster. Filter LCK_NONBLOCK in clvmd lock_vg.
2006-05-12 23:16:48 +04:00
#define DEFAULT_DMEVENTD_MONITOR 1
Add a [--poll {y|n}] flag to vgchange and lvchange to control whether the background polldaemon is allowed to start. It can be used standalone or in conjunction with --refresh or --available y. Control over when the background polldaemon starts will be particularly important for snapshot-merge of a root filesystem. Dracut will be updated to activate all LVs with: --poll n The lvm2-monitor initscript will start polling with: --poll y NOTE: Because we currently have no way of knowing if a background polldaemon is active for a given LV the following limitations exist and have been deemed acceptable: 1) it is not possible to stop an active polldaemon; so the lvm2-monitor initscript doesn't stop running polldaemon(s) 2) redundant polldaemon instances will be started for all specified LVs if vgchange or lvchange are repeatedly used with '--poll y' Signed-off-by: Mike Snitzer <snitzer@redhat.com>
2010-01-05 23:56:51 +03:00
#define DEFAULT_BACKGROUND_POLLING 1
Add config file setting: dmeventd/mirror_library
2006-01-27 22:05:05 +03:00
config: fix compile error in config-settings.h if using --disable-dmeventd config/config_settings.h:257:102: error: 'DMEVENTD_PATH' undeclared here (not in a function)
2014-03-31 17:57:30 +04:00
#ifndef DMEVENTD_PATH
thin: Support thin_check --clear-needs-check-flag. Update thin provisioning tools to version 0.3.2 or later!
2014-04-04 05:22:40 +04:00
# define DEFAULT_DMEVENTD_PATH ""
config: fix compile error in config-settings.h if using --disable-dmeventd config/config_settings.h:257:102: error: 'DMEVENTD_PATH' undeclared here (not in a function)
2014-03-31 17:57:30 +04:00
#else
thin: Support thin_check --clear-needs-check-flag. Update thin provisioning tools to version 0.3.2 or later!
2014-04-04 05:22:40 +04:00
# define DEFAULT_DMEVENTD_PATH DMEVENTD_PATH
#endif
#ifdef THIN_CHECK_NEEDS_CHECK
config: fix check_options array The code used it as both a single string, and as an array of strings in different places. Fix it so that it's an array of strings everywhere.
2015-04-23 18:35:34 +03:00
# define DEFAULT_THIN_CHECK_OPTION1 "-q"
# define DEFAULT_THIN_CHECK_OPTION2 "--clear-needs-check-flag"
config: cleanup default values for some configuration settings with array values Do not use "#S" (blank string) as default value as that ends up with 'key = [ "" ]' to be generated which is not what we want in most cases. Also, fix default values for global/{thin,cache}_{check,repair}_options and avoid assigning blank values. For example, the thin_check_options had this set as default value previously: "#S" DEFAULT_THIN_CHECK_OPTION1 "#S" DEFAULT_THIN_CHECK_OPTION2 If any (or both) of DEFAULT_THIN_CHECK_OPTION* variables was set to "", we ended up with clumsy default value generated like: thin_check_options = [ "-q", "" ] With this patch, we end up with correct: thin_check_options = [ "-q" ] or, if all options are undefined: thin_check_options = [ ] Which is the correct way to express this.
2015-06-23 14:18:53 +03:00
# define DEFAULT_THIN_CHECK_OPTIONS_CONFIG "#S" DEFAULT_THIN_CHECK_OPTION1 "#S" DEFAULT_THIN_CHECK_OPTION2
thin: Support thin_check --clear-needs-check-flag. Update thin provisioning tools to version 0.3.2 or later!
2014-04-04 05:22:40 +04:00
#else
config: fix check_options array The code used it as both a single string, and as an array of strings in different places. Fix it so that it's an array of strings everywhere.
2015-04-23 18:35:34 +03:00
# define DEFAULT_THIN_CHECK_OPTION1 "-q"
# define DEFAULT_THIN_CHECK_OPTION2 ""
config: cleanup default values for some configuration settings with array values Do not use "#S" (blank string) as default value as that ends up with 'key = [ "" ]' to be generated which is not what we want in most cases. Also, fix default values for global/{thin,cache}_{check,repair}_options and avoid assigning blank values. For example, the thin_check_options had this set as default value previously: "#S" DEFAULT_THIN_CHECK_OPTION1 "#S" DEFAULT_THIN_CHECK_OPTION2 If any (or both) of DEFAULT_THIN_CHECK_OPTION* variables was set to "", we ended up with clumsy default value generated like: thin_check_options = [ "-q", "" ] With this patch, we end up with correct: thin_check_options = [ "-q" ] or, if all options are undefined: thin_check_options = [ ] Which is the correct way to express this.
2015-06-23 14:18:53 +03:00
# define DEFAULT_THIN_CHECK_OPTIONS_CONFIG "#S" DEFAULT_THIN_CHECK_OPTION1
config: fix compile error in config-settings.h if using --disable-dmeventd config/config_settings.h:257:102: error: 'DMEVENTD_PATH' undeclared here (not in a function)
2014-03-31 17:57:30 +04:00
#endif
config: {thin,cache}_{check,repair}_options are never undefined Require global/{thin,cache}_{check,repair}_options to be always defined. If not defined directly by user in the configuration and if there's no concrete default option to use, make "" (empty string) the default one - it's then clearly visible in the "lvmconfig --type default" (and generated lvm.conf) and also it makes its handling in the code more straightforward so we don't need to handle undefined values. This means, if there are no default values for these settings defined, we end up with this generated now: {thin,cache}_{check,repair}_options = [ "" ] So the value is never undefined and if it is, it's an error. (The cache_repair_options is actually not used in the code at the moment, but once the code using this setting is in, it will follow the same logic as used for thin_repair_options.)
2015-07-14 11:03:19 +03:00
#define DEFAULT_THIN_REPAIR_OPTION1 ""
#define DEFAULT_THIN_REPAIR_OPTIONS_CONFIG "#S" DEFAULT_THIN_REPAIR_OPTION1
Thin add thin_pool_metadata_require_separate_pvs Allow to set different policy for pool from mirrors.
2011-11-05 02:44:21 +04:00
#define DEFAULT_THIN_POOL_METADATA_REQUIRE_SEPARATE_PVS 0
thin: improve 16g support for thin pool metadata Initial support for thin-pool used slightly smaller max size 15.81GiB for thin-pool metadata. However the real limit later settled at 15.88GiB (difference is ~64MiB - 16448 4K blocks). lvm2 could not simply increase the size as it has been using hard cropping of the loaded metadata device to avoid warnings printing warning of kernel when the size was bigger (i.e. due to bigger extent_size). This patch adds the new lvm.conf configurable setting: allocation/thin_pool_crop_metadata which defaults to 0 -> no crop of metadata beyond 15.81GiB. Only user with these sizes of metadata will be affected. Without cropping lvm2 now limits metadata allocation size to 15.88GiB. Any space beyond is currently not used by thin-pool target. Even if i.e. bigger LV is used for metadata via lvconvert, or allocated bigger because of to large extent size. With cropping enabled (=1) lvm2 preserves the old limitation 15.81GiB and should allow to work in the evironement with older lvm2 tools (i.e. older distribution). Thin-pool metadata with size bigger then 15.81G is now using CROP_METADATA flag within lvm2 metadata, so older lvm2 recognizes an incompatible thin-pool and cannot activate such pool! Users should use uncropped version as it is not suffering from various issues between thin_repair results and allocated metadata LV as thin_repair limit is 15.88GiB Users should use cropping only when really needed! Patch also better handles resize of thin-pool metadata and prevents resize beoyond usable size 15.88GiB. Resize beyond 15.81GiB automatically switches pool to no-crop version. Even with existing bigger thin-pool metadata command 'lvextend -l+1 vg/pool_tmeta' does the change. Patch gives better controls 'coverted' metadata LV and reports less confusing message during conversion. Patch set also moves the code for updating min/max into pool_manip.c for better sharing with cache_pool code.
2021-01-12 19:59:29 +03:00
#define DEFAULT_THIN_POOL_CROP_METADATA 0
#define DEFAULT_THIN_POOL_MAX_METADATA_SIZE_V1_KB (UINT64_C(255) * ((1 << 14) - 64) * 4) /* KB */ /* 0x3f8040 blocks */
cleanup: use DM limit define For calculation use already defined size in libdm, which give better estimation of maximal size of thin pool metadata.
2017-06-05 12:26:01 +03:00
#define DEFAULT_THIN_POOL_MAX_METADATA_SIZE (DM_THIN_MAX_METADATA_SIZE / 2) /* KB */
Thin supports poolmetadatasize setting Add option to set pool metadatasize. For passing size parameter reuse region_size.
2011-11-05 02:43:10 +04:00
#define DEFAULT_THIN_POOL_MIN_METADATA_SIZE 2048 /* KB */
cleanup: define really uses KB Cleanup also units for DEFAULT_THIN_POOL_OPTIMAL_METADATA_SIZE define (128MB) and update calcs for it.
2017-06-09 22:29:34 +03:00
#define DEFAULT_THIN_POOL_OPTIMAL_METADATA_SIZE (128 * 1024) /* KB */
thin: rename thin_pool_chunk_size_calculation -> ..size_policy and rename "default" policy to "generic" Just to be consistent with existing naming we use.
2013-10-04 14:30:33 +04:00
#define DEFAULT_THIN_POOL_CHUNK_SIZE_POLICY "generic"
thin: support configurable thin pool defaults Configurable settings for thin pool create if they are not specified on command line. New supported lvm.conf options are: allocation/thin_pool_chunk_size allocation/thin_pool_discards allocation/thin_pool_zero
2012-11-26 14:20:13 +04:00
#define DEFAULT_THIN_POOL_CHUNK_SIZE 64 /* KB */
thin: use appropriate default value based on allocation/thin_pool_chunk_size_calculation setting If thin_pool_chunk_size_calculation is set to "default", use 64KiB, otheriwse 512KiB for "performance".
2013-09-25 18:00:52 +04:00
#define DEFAULT_THIN_POOL_CHUNK_SIZE_PERFORMANCE 512 /* KB */
thin: max thin
2019-01-29 20:45:52 +03:00
/* Chunk size big enough it no longer needs jump by power-of-2 */
#define DEFAULT_THIN_POOL_CHUNK_SIZE_ALIGNED 1024 /* KB */
thin: support configurable thin pool defaults Configurable settings for thin pool create if they are not specified on command line. New supported lvm.conf options are: allocation/thin_pool_chunk_size allocation/thin_pool_discards allocation/thin_pool_zero
2012-11-26 14:20:13 +04:00
#define DEFAULT_THIN_POOL_DISCARDS "passdown"
#define DEFAULT_THIN_POOL_ZERO 1
cache: Code changes to allow creation of cache pools This patch allows the creation and removal of cache pools. Users are not yet able to create cache LVs. They are only able to define the space used for the cache and its characteristics (chunk_size and cache mode ATM) by creating the cache pool.
2014-02-04 21:57:08 +04:00
#define DEFAULT_POOL_METADATA_SPARE 1 /* thin + cache */
pool: zero metadata To avoid polution of metadata with some 'garbage' content or eventualy some leak of stale data in case user want to upload metadata somewhere, ensure upon allocation the metadata device is fully zeroed. Behaviour may slow down allocation of thin-pool or cache-pool a bit so the old behaviour can be restored with lvm.conf setting: allocation/zero_metadata=0 TODO: add zeroing for extension of metadata volume.
2020-06-24 13:11:21 +03:00
#define DEFAULT_ZERO_METADATA 1 /* thin + cache */
Thin supports poolmetadatasize setting Add option to set pool metadatasize. For passing size parameter reuse region_size.
2011-11-05 02:43:10 +04:00
cache: support clear-needs-check Support newer cache tool which support new option --clear-needs-check-flag. Code does same as for thin_check.
2015-07-07 10:51:40 +03:00
#ifdef CACHE_CHECK_NEEDS_CHECK
# define DEFAULT_CACHE_CHECK_OPTION1 "-q"
# define DEFAULT_CACHE_CHECK_OPTION2 "--clear-needs-check-flag"
# define DEFAULT_CACHE_CHECK_OPTIONS_CONFIG "#S" DEFAULT_CACHE_CHECK_OPTION1 "#S" DEFAULT_CACHE_CHECK_OPTION2
#else
# define DEFAULT_CACHE_CHECK_OPTION1 "-q"
# define DEFAULT_CACHE_CHECK_OPTION2 ""
# define DEFAULT_CACHE_CHECK_OPTIONS_CONFIG "#S" DEFAULT_CACHE_CHECK_OPTION1
#endif
config: {thin,cache}_{check,repair}_options are never undefined Require global/{thin,cache}_{check,repair}_options to be always defined. If not defined directly by user in the configuration and if there's no concrete default option to use, make "" (empty string) the default one - it's then clearly visible in the "lvmconfig --type default" (and generated lvm.conf) and also it makes its handling in the code more straightforward so we don't need to handle undefined values. This means, if there are no default values for these settings defined, we end up with this generated now: {thin,cache}_{check,repair}_options = [ "" ] So the value is never undefined and if it is, it's an error. (The cache_repair_options is actually not used in the code at the moment, but once the code using this setting is in, it will follow the same logic as used for thin_repair_options.)
2015-07-14 11:03:19 +03:00
#define DEFAULT_CACHE_REPAIR_OPTION1 ""
#define DEFAULT_CACHE_REPAIR_OPTIONS_CONFIG "#S" DEFAULT_CACHE_REPAIR_OPTION1
cache: Allocation code changes necessary to support cache_pool Cache pools require a data and metadata area (like thin pools). Unlike thin pool, if 'cache_pool_metadata_require_separate_pvs' is not set to '1', the metadata and data area will be allocated from the same device. It is also done in a manner similar to RAID, where a single chunk of space is allocated and then split to form the metadata and data device - ensuring that they are together.
2014-01-28 22:25:02 +04:00
#define DEFAULT_CACHE_POOL_METADATA_REQUIRE_SEPARATE_PVS 0
pool: Make another thin pool fn generic for cache usage also Make '_recalculate_thin_pool_chunk_size_with_dev_hints' so it can be used for cache and thin pools.
2014-02-04 17:03:52 +04:00
#define DEFAULT_CACHE_POOL_CHUNK_SIZE 64 /* KB */
cache: introduce cache_pool_max_chunks Introduce 'hard limit' for max number of cache chunks. When cache target operates with too many chunks (>10e6). When user is aware of related possible troubles he may increase the limit in lvm.conf. Also verbosely inform user about possible solution. Code works for both lvcreate and lvconvert. Lvconvert fully supports change of chunk_size when caching LV (and validates for compatible settings).
2016-08-24 11:16:01 +03:00
#define DEFAULT_CACHE_POOL_MAX_CHUNKS 1000000
cache pool: Add 'update_cache_pool_params' Similar function to 'update_thin_pool_params', but for cache. Performs the adjustements for chunk_size, metdata device size, etc.
2014-02-04 21:50:27 +04:00
#define DEFAULT_CACHE_POOL_MIN_METADATA_SIZE 2048 /* KB */
#define DEFAULT_CACHE_POOL_MAX_METADATA_SIZE (16 * 1024 * 1024) /* KB */
cache: add cache_policy cache_settings Add new profilable configurables: allocation/cache_policy allocation/cache_settings and mark allocation/cache_pool_chunk_size as profilable as well. Obsolete allocation/cache_pool_cachemode and introduce new allocation/cache_mode instead. Rename DEFAULT_CACHE_POOL_POLICY to DEFAULT_CACHE_POLICY.
2015-07-20 12:44:15 +03:00
#define DEFAULT_CACHE_POLICY "mq"
cache: introduce allocation/cache_metadata_format Add new profilable configation setting to let user select which metadata format of a created cache pool he wish to use. By default the 'best' available format is autodetected at runtime, but user may enforce format 1 or 2 ATM. Code also detects availability for metadata2 supporting cache target. In case of troubles user may easily Disable usage of this feature by placing 'metadata2' into global/cache_disabled_features list.
2017-02-26 22:19:07 +03:00
#define DEFAULT_CACHE_METADATA_FORMAT CACHE_METADATA_FORMAT_UNSELECTED /* Autodetect */
cache: add cache_policy cache_settings Add new profilable configurables: allocation/cache_policy allocation/cache_settings and mark allocation/cache_pool_chunk_size as profilable as well. Obsolete allocation/cache_pool_cachemode and introduce new allocation/cache_mode instead. Rename DEFAULT_CACHE_POOL_POLICY to DEFAULT_CACHE_POLICY.
2015-07-20 12:44:15 +03:00
#define DEFAULT_CACHE_MODE "writethrough"
cache: Allocation code changes necessary to support cache_pool Cache pools require a data and metadata area (like thin pools). Unlike thin pool, if 'cache_pool_metadata_require_separate_pvs' is not set to '1', the metadata and data area will be allocated from the same device. It is also done in a manner similar to RAID, where a single chunk of space is allocated and then split to form the metadata and data device - ensuring that they are together.
2014-01-28 22:25:02 +04:00
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
/* VDO defaults */
#define DEFAULT_VDO_USE_COMPRESSION (true)
#define DEFAULT_VDO_USE_DEDUPLICATION (true)
lib: move towards v2 version of VDO format Drop very old original format of VDO target and focus on V2 version. So some variables were renamed or replaced. There is no compatibility preserved (with assumption so far this is experimental feature and there is no real user). Note - version currently VDO calls this version 6.2.
2018-12-20 15:17:30 +03:00
#define DEFAULT_VDO_USE_METADATA_HINTS (true)
#define DEFAULT_VDO_MINIMUM_IO_SIZE (4096)
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
#define DEFAULT_VDO_BLOCK_MAP_CACHE_SIZE_MB (DM_VDO_BLOCK_MAP_CACHE_SIZE_MINIMUM_MB)
lib: move towards v2 version of VDO format Drop very old original format of VDO target and focus on V2 version. So some variables were renamed or replaced. There is no compatibility preserved (with assumption so far this is experimental feature and there is no real user). Note - version currently VDO calls this version 6.2.
2018-12-20 15:17:30 +03:00
#define DEFAULT_VDO_BLOCK_MAP_ERA_LENGTH (DM_VDO_BLOCK_MAP_ERA_LENGTH_MAXIMUM)
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
#define DEFAULT_VDO_USE_SPARSE_INDEX (false)
#define DEFAULT_VDO_CHECK_POINT_FREQUENCY (0)
#define DEFAULT_VDO_INDEX_MEMORY_SIZE_MB (DM_VDO_INDEX_MEMORY_SIZE_MINIMUM_MB)
#define DEFAULT_VDO_SLAB_SIZE_MB (2 * 1024) // 2GiB ... 19 slabbits
#define DEFAULT_VDO_ACK_THREADS (1)
vdo: raise VDO default bio threads to 4 Since 'vdo create' tends to use this setting, update lvm2 to provide same default.
2019-10-04 15:52:40 +03:00
#define DEFAULT_VDO_BIO_THREADS (4)
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
#define DEFAULT_VDO_BIO_ROTATION (64)
#define DEFAULT_VDO_CPU_THREADS (2)
#define DEFAULT_VDO_HASH_ZONE_THREADS (1)
#define DEFAULT_VDO_LOGICAL_THREADS (1)
#define DEFAULT_VDO_PHYSICAL_THREADS (1)
#define DEFAULT_VDO_WRITE_POLICY "auto"
lib: move towards v2 version of VDO format Drop very old original format of VDO target and focus on V2 version. So some variables were renamed or replaced. There is no compatibility preserved (with assumption so far this is experimental feature and there is no real user). Note - version currently VDO calls this version 6.2.
2018-12-20 15:17:30 +03:00
#define DEFAULT_VDO_MAX_DISCARD (DM_VDO_MAX_DISCARD_MINIMUM)
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
#define DEFAULT_VDO_FORMAT_OPTIONS_CONFIG "#S" ""
/*
* VDO pool will reverve some sectors in the front and the back of pool device to avoid
* seeing same device twice in the system.
*/
vdo: support vdo_pool_header_size Add profilable configurable setting for vdo pool header size, that is used as 'extra' empty space at the front and end of vdo-pool device to avoid having a disk in the system the may have same data is real vdo LV. For some conversion cases however we may need to allow using '0' header size. TODO: in this case we may eventually avoid adding 'linear' mapping layer in future - but this requires further modification over lvm code base.
2021-06-28 18:53:08 +03:00
#define DEFAULT_VDO_POOL_HEADER_SIZE_KB (512)
lib: new vdo segment configurable options Configurable for vdo segment with their default values. Also specify their ranges with minimal and maximal values.
2018-06-29 12:09:03 +03:00
fsadm: support configurable full path Just like with other tools lvm2 is using allow to define fully configurable path. Default is selected by $PREFIX/sbin/fsadm
2017-04-08 20:43:20 +03:00
#define DEFAULT_FSADM_PATH FSADM_PATH
o Rename many occurrences of 'backup' to 'archive' to reduce confusion. o Extract file creation/renaming code into a library and change backup code to use it too. o Support umask. o Bring lvm.conf man page up-to-date.
2002-01-09 22:16:48 +03:00
#define DEFAULT_UMASK 0077
Correct example.conf to indicate that lvm2 not lvm1 is the default format. Remove an unused stray LVM1_SUPPORT ifdef.
2009-10-05 16:44:20 +04:00
#define DEFAULT_FORMAT "lvm2"
Merge with text format branch. Lots of changes/very little testing so far => there'll be bugs! Use 'vgcreate -M text' to create a volume group with its metadata stored in text files. Text format metadata changes should be reasonably atomic, with a (basic) automatic recovery mechanism if the system crashes while a change is in progress. Add a metadata section to lvm.conf to specify multiple directories if you want (recommended) to keep multiple copies of the metadata (eg on different filesystems). e.g. metadata { dirs = ["/etc/lvm/metadata1","/usr/local/lvm/metadata2"] } Plenty of refinements still in the pipeline.
2002-04-24 22:20:51 +04:00
Default stripesize 64k & config file setting for it; Clear many compiler warnings (i386) & associated bugs - hopefully without introducing too many new bugs:-) (Same exercise required for other archs.) Default compilation has optimisation - or else use ./configure --enable-debug
2002-12-20 02:25:55 +03:00
#define DEFAULT_STRIPESIZE 64 /* KB */
conf: add metadata/record_lvs_history configuration setting The metadata/record_lvs_history is global switch which enables or disables recording historical LVs in metadata. If both metadata/record_lvs_history=1 lvm.conf option and --nohistory command switch is used at the same time, the --nohistory prevails.
2016-03-01 17:25:49 +03:00
#define DEFAULT_RECORD_LVS_HISTORY 0
conf: add metadata/lvs_history_timeout configuration setting
2016-03-01 17:29:27 +03:00
#define DEFAULT_LVS_HISTORY_RETENTION_TIME 0
Add --metadataignore to pvcreate. Allow metadataignore flag to be passed in to pvcreate. Ideally, more refactoring of the mda allocation / initialization is warranted, but for now, we just add another parameter to 'add_mda' to take an existing mda ignored flag. We need to do this or pv_write loses the state of the mda 'ignored' flag before copying and writing to disk.
2010-06-30 16:17:24 +04:00
#define DEFAULT_PVMETADATAIGNORE 0
Refactoring.
2002-11-18 17:01:16 +03:00
#define DEFAULT_PVMETADATACOPIES 1
Add mda_copies to VG structures and initialization. Add a field to struct volume_group to later implement metadata balancing: - mda_copies: target # of non-ignored mdas in the VG; default 0 (do not control pv 'ignore mdas' bit. This patch just adds the parameter to the structures with the default values but does not modify any commands. Should be no functional change. Signed-off-by: Dave Wysochanski <dwysocha@redhat.com>
2010-06-29 00:36:37 +04:00
#define DEFAULT_VGMETADATACOPIES 0
Tidy various pre-processing incl. making libdl optional.
2003-03-24 21:08:53 +03:00
#define DEFAULT_LABELSECTOR UINT64_C(1)
Enhance the management of readahead settings.
2007-11-09 19:51:54 +03:00
#define DEFAULT_READ_AHEAD "auto"
Add activation/udev_rules config option in lvm.conf. Add dm_tree_add_dev_with_udev_flags to provide wider support for udev flags.
2010-01-07 22:54:21 +03:00
#define DEFAULT_UDEV_RULES 1
Change DEFAULT_UDEV_SYNC to 1 so udev_sync is used even without any config. This should be set by default! Normally we have "activation/udev_sync = 1" in lvm.conf (example.conf.in). But if we use lvm2 without any config file (or without a definition within '--config' option) the DEFAULT_UDEV_SYNC is used instead. Together with verify_udev_operations=0 (when we rely on udev fully), this can cause races as the node could be missing when needed. (See also https://bugzilla.redhat.com/show_bug.cgi?id=723144)
2011-08-02 14:49:57 +04:00
#define DEFAULT_UDEV_SYNC 1
dbus: add notification from commands When a command modifies a PV or VG, or changes the activation state of an LV, it will send a dbus notification when the command is finished. This can be enabled/disabled with a config setting.
2016-02-22 18:42:03 +03:00
#define DEFAULT_NOTIFY_DBUS 1
Move udev_only logic inside stacked node op code. (We still need to treat add+readhead+del as a no-op.) Rename udev_fallback to verify_udev_operations. Rename --udevfallback to --verifyudev
2011-06-28 01:43:58 +04:00
#define DEFAULT_VERIFY_UDEV_OPERATIONS 0
Add activation/retry_deactivation to lvm.conf to retry deactivation of an LV.
2011-09-22 21:39:56 +04:00
#define DEFAULT_RETRY_DEACTIVATION 1
Add framework for validation of ioctls. Doesn't do any checks yet. dmsetup --checks libdevmapper: dm_task_enable_checks() lvm.conf: activation/checks=1
2011-07-01 18:09:19 +04:00
#define DEFAULT_ACTIVATION_CHECKS 0
fix default extent_size
2008-01-17 18:31:18 +03:00
#define DEFAULT_EXTENT_SIZE 4096 /* In KB */
Add defines for default vgcreate parameters.
2009-07-09 14:00:36 +04:00
#define DEFAULT_MAX_PV 0
#define DEFAULT_MAX_LV 0
#define DEFAULT_ALLOC_POLICY ALLOC_NORMAL
Various changes to the allocation algorithms: Expect some fallout. There is a lot to test. Two new config settings added that are intended to make the code behave closely to the way it did before - worth a try if you find problems.
2011-02-27 03:38:31 +03:00
#define DEFAULT_MIRROR_LOGS_REQUIRE_SEPARATE_PVS 0
#define DEFAULT_MAXIMISE_CLING 1
Add defines for default vgcreate parameters.
2009-07-09 14:00:36 +04:00
#define DEFAULT_CLUSTERED 0
Default values for some display output settings
2002-05-07 16:50:01 +04:00
Refactoring.
2002-11-18 17:01:16 +03:00
#define DEFAULT_MSG_PREFIX " "
Default values for some display output settings
2002-05-07 16:50:01 +04:00
#define DEFAULT_CMD_NAME 0
Refactoring.
2002-11-18 17:01:16 +03:00
#define DEFAULT_OVERWRITE 0
#ifndef DEFAULT_LOG_FACILITY
Improve build robustness.
2003-04-15 17:24:42 +04:00
# define DEFAULT_LOG_FACILITY LOG_USER
Refactoring.
2002-11-18 17:01:16 +03:00
#endif
conf: add log/report_command_log config setting
2016-06-14 12:58:01 +03:00
#define DEFAULT_COMMAND_LOG_REPORT 0
Refactoring.
2002-11-18 17:01:16 +03:00
#define DEFAULT_SYSLOG 1
#define DEFAULT_VERBOSE 0
config: add silent mode Accept -q as the short form of --quiet. Suppress non-essential standard output if -q is given twice. Treat log/silent in lvm.conf as equivalent to -qq. Review all log_print messages and change some to log_print_unless_silent. When silent, the following commands still produce output: dumpconfig, lvdisplay, lvmdiskscan, lvs, pvck, pvdisplay, pvs, version, vgcfgrestore -l, vgdisplay, vgs. [Needs checking.] Non-essential messages are shifted from log level 4 to log level 5 for syslog and lvm2_log_fn purposes.
2012-08-25 23:35:48 +04:00
#define DEFAULT_SILENT 0
Refactoring.
2002-11-18 17:01:16 +03:00
#define DEFAULT_LOGLEVEL 0
logging: add command[pid] and timestamp to file and verbose output Without this, the output from different commands in a single log file could not be separated. Change the default "indent" setting to 0 so that the default debug output does not include variable spaces in the middle of debug lines.
2019-02-22 21:01:20 +03:00
#define DEFAULT_INDENT 0
Optionally abort on internal errors (and leverage this option in the testsuite). (This is showing a problem in the pvmove test for me, so I expect the tests to start failing -- this needs to be fixed separately though.)
2009-11-30 20:17:11 +03:00
#define DEFAULT_ABORT_ON_INTERNAL_ERRORS 0
libdm: add human R|readable units When showing sizes with 'H|human' units we do use standard rounding. This however is confusing users from time to time, when the printed number uses some biger units i.e. GiB and there is just tiny fraction of space missing. So here is some real-life example with new 'r' unit. $lvs LV VG Attr LSize Pool Origin lvol0 vg -wi-a----- 1.99g lvol1 vg -wi-a----- <2.00g lvol2 vg -wi-a----- <2.01g Meaning is - lvol1 has 'slightly' less then 2.00g - from sign '<' user can be aware the LV doesn't have full 2.00GiB in size so he will be less surpriced allocation of 2G volume will not succeed. $ vgs VG #PV #LV #SN Attr VSize VFree vg 2 2 0 wz--n- <6,00g <2,01g For uses needing 'old' undecorated human unit simply will continue to use 'H|h' units. The new R|r may further change when we would recongnize some other way how to improve readability.
2017-01-09 18:30:49 +03:00
#define DEFAULT_UNITS "r"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_SUFFIX 1
host tags
2004-03-08 21:13:22 +03:00
#define DEFAULT_HOSTTAGS 0
Refactoring.
2002-11-18 17:01:16 +03:00
Add global/si_unit_consistency to enable cleaned-up use of units in output. Add configure --enable-units-compat to set si_unit_consistency off by default. Use standard output units for 'PE Size' and 'Stripe size' in pv/lvdisplay.
2009-09-28 20:23:44 +04:00
#ifndef DEFAULT_SI_UNIT_CONSISTENCY
# define DEFAULT_SI_UNIT_CONSISTENCY 1
#endif
configure --disable-devmapper if you don't have libdevmapper
2003-01-09 01:44:07 +03:00
#ifdef DEVMAPPER_SUPPORT
Improve build robustness.
2003-04-15 17:24:42 +04:00
# define DEFAULT_ACTIVATION 1
configure --disable-devmapper if you don't have libdevmapper
2003-01-09 01:44:07 +03:00
#else
Improve build robustness.
2003-04-15 17:24:42 +04:00
# define DEFAULT_ACTIVATION 0
configure --disable-devmapper if you don't have libdevmapper
2003-01-09 01:44:07 +03:00
#endif
Default values for some display output settings
2002-05-07 16:50:01 +04:00
release 2.02.103 52 files changed, 598 insertions(+), 264 deletions(-)
2013-10-04 17:32:23 +04:00
#define DEFAULT_RESERVED_MEMORY 8192
#define DEFAULT_RESERVED_STACK 64 /* KB */
#define DEFAULT_PROCESS_PRIORITY -18
fix: make it possible to compile with --disable-devmapper again Some code has been added recently which makes it impossible to compile when "configure --disable-devmapper" is used. This patch just shuffles the code around so it's under proper #ifdef DEVMAPPER_SUPPORT.
2013-09-27 15:58:55 +04:00
conf: add activation/auto_set_activation_skip The activation/auto_set_activation_skip enables/disables automatic adding of the ACTIVATION_SKIP LV flag. By default thin snapshots are flagged to be skipped during activation. And by default, the auto_set_activation_skip is enabled.
2013-07-12 11:27:17 +04:00
#define DEFAULT_AUTO_SET_ACTIVATION_SKIP 1
activation: Add "degraded" activation mode Currently, we have two modes of activation, an unnamed nominal mode (which I will refer to as "complete") and "partial" mode. The "complete" mode requires that a volume group be 'complete' - that is, no missing PVs. If there are any missing PVs, no affected LVs are allowed to activate - even RAID LVs which might be able to tolerate a failure. The "partial" mode allows anything to be activated (or at least attempted). If a non-redundant LV is missing a portion of its addressable space due to a device failure, it will be replaced with an error target. RAID LVs will either activate or fail to activate depending on how badly their redundancy is compromised. This patch adds a third option, "degraded" mode. This mode can be selected via the '--activationmode {complete|degraded|partial}' option to lvchange/vgchange. It can also be set in lvm.conf. The "degraded" activation mode allows RAID LVs with a sufficient level of redundancy to activate (e.g. a RAID5 LV with one device failure, a RAID6 with two device failures, or RAID1 with n-1 failures). RAID LVs with too many device failures are not allowed to activate - nor are any non-redundant LVs that may have been affected. This patch also makes the "degraded" mode the default activation mode. The degraded activation mode does not yet work in a cluster. A new cluster lock flag (LCK_DEGRADED_MODE) will need to be created to make that work. Currently, there is limited space for this extra flag and I am looking for possible solutions. One possible solution is to usurp LCK_CONVERT, as it is not used. When the locking_type is 3, the degraded mode flag simply gets dropped and the old ("complete") behavior is exhibited.
2014-07-10 07:56:11 +04:00
#define DEFAULT_ACTIVATION_MODE "degraded"
Add activation/use_linear_target enabled by default. (prajnoha) LVM metadata knows only of striped segments - not linear ones. The activation code detects segments with a single stripe and switches them to use the linear target. If the new lvm.conf setting is set to 0 (e.g. in a test script), this 'optimisation' is turned off.
2011-11-29 00:37:51 +04:00
#define DEFAULT_USE_LINEAR_TARGET 1
Improve the way VGs with PVs missing are handled so manual intervention is required in fewer circumstances. (mornfall)
2008-09-19 10:42:00 +04:00
#define DEFAULT_STRIPE_FILLER "error"
lvcreate: raise default raid regionsize to 2MiB Related: rhbz1392947.
2017-04-13 17:10:49 +03:00
#define DEFAULT_RAID_REGION_SIZE 2048 /* KB */
add region size & interval
2003-04-30 19:27:48 +04:00
#define DEFAULT_INTERVAL 15
stripe filler parameter
2003-04-25 02:10:56 +04:00
config: make DEFAULT_MAX_HISTORY unconditional
2013-03-06 15:47:23 +04:00
#define DEFAULT_MAX_HISTORY 100
Another attempt to support both readline versions.
2002-01-08 22:17:08 +03:00
config: add report/compact_output lvm.conf setting to enable or isable field compacting $ lvm dumpconfig report/compact_output compact_output=0 $ lvs vg LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 vg owi-a-s--- 4.00m lvol1 vg -wi-a----- 4.00m lvol2 vg swi-a-s--- 4.00m lvol0 0.00 $ lvm dumpconfig report/compact_output compact_output=1 $ lvs vg LV VG Attr LSize Origin Data% lvol0 vg owi-a-s--- 4.00m lvol1 vg -wi-a----- 4.00m lvol2 vg swi-a-s--- 4.00m lvol0 0.00
2014-12-05 13:46:26 +03:00
#define DEFAULT_REP_COMPACT_OUTPUT 0
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_REP_ALIGNED 1
#define DEFAULT_REP_BUFFERED 1
Add --rows to reports.
2008-06-25 02:48:53 +04:00
#define DEFAULT_REP_COLUMNS_AS_ROWS 0
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_REP_HEADINGS 1
Add --prefixes to reporting tools for field name prefix output format. E.g. lvs --prefixes --noheadings --unbuffered --units m --nosuffix (Used '--prefixes' for now, but I'm looking for a better name.)
2008-04-20 04:15:08 +04:00
#define DEFAULT_REP_PREFIXES 0
Add --unquoted to reporting tools.
2008-06-25 01:21:04 +04:00
#define DEFAULT_REP_QUOTED 1
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_REP_SEPARATOR " "
conf: add report/list_item_separator lvm.conf option For example: $ lvm dumpconfig report/list_item_separator list_item_separator="," $ lvs -o name,tags vg/lvol1 LV LV Tags lvol1 a,x,y $ lvm dumpconfig report/list_item_separator list_item_separator=":" $ lvs -o name,tags vg/lvol1 LV LV Tags lvol1 a:x:y
2014-07-10 18:18:45 +04:00
#define DEFAULT_REP_LIST_ITEM_SEPARATOR ","
conf: make time format configurable Make it possible to define format for time that is displayed. The way the format is defined is equal to the way that is used for strftime function, although not all formatting options as used in strftime are available for LVM2 - the set is restricted (e.g. we do not allow newline to be printed). The lvm.conf comments contain the whole list that LVM2 accepts for time format together with brief description (copied from strftime man page). For example: (defaults used - the format is the same as used before this patch) $ lvs -o+time vg/lvol0 vg/lvol1 LV VG Attr LSize Time lvol0 vg -wi-a----- 4.00m 2015-06-25 16:18:34 +0200 lvol1 vg -wi-a----- 4.00m 2015-06-29 09:17:11 +0200 (using 'time_format = "@%s"' in lvm.conf - number of seconds since the Epoch) $ lvs -o+time vg/lvol0 vg/lvol1 LV VG Attr LSize Time lvol0 vg -wi-a----- 4.00m @1435241914 lvol1 vg -wi-a----- 4.00m @1435562231
2015-05-25 17:13:07 +03:00
#define DEFAULT_TIME_FORMAT "%Y-%m-%d %T %z"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
conf: add report/output_format config setting New report/output_format configuration sets the output format used for all LVM commands globally. Currently, there are 2 formats recognized: - basic (the classical basic output with columns and rows, used by default) - json (output is in json format)
2016-05-24 13:05:42 +03:00
#define DEFAULT_REP_OUTPUT_FORMAT "basic"
config: add report/compact_output_cols to control which columns to compact in report output The new report/compact_output_cols setting has exactly the same effect as report/compact_output setting. The difference is that with the new setting it's possible to define which cols should be compacted exactly in contrast to all cols in case of report/compact_output. In case both compact_output and compact_output_cols is enabled/set, the compact_output prevails. For example: $ lvmconfig --type full report/compact_output report/compact_output_cols compact_output=0 compact_output_cols="" $ lvs vg LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert lvol0 vg -wi-a----- 4.00m --- $ lvmconfig --type full report/compact_output report/compact_output_cols compact_output=0 compact_output_cols="data_percent,metadata_percent,pool_lv,move_pv,origin" $ lvs vg LV VG Attr LSize Log Cpy%Sync Convert lvol0 vg -wi-a----- 4.00m --- $ lvmconfig --type full report/compact_output report/compact_output_cols compact_output=1 compact_output_cols="data_percent,metadata_percent,pool_lv,move_pv,origin" $ lvs vg LV VG Attr LSize lvol0 vg -wi-a----- 4.00m
2015-10-16 17:25:51 +03:00
#define DEFAULT_COMPACT_OUTPUT_COLS ""
conf: add log/command_log_selection config setting
2016-06-14 14:25:03 +03:00
#define DEFAULT_COMMAND_LOG_SELECTION "!(log_type=status && message=success)"
report: Add metadata_percent to lvs_cols.
2014-05-15 11:32:27 +04:00
#define DEFAULT_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"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_VGS_COLS "vg_name,pv_count,lv_count,snap_count,vg_attr,vg_size,vg_free"
#define DEFAULT_PVS_COLS "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free"
#define DEFAULT_SEGS_COLS "lv_name,vg_name,lv_attr,stripes,segtype,seg_size"
Initial pv_segment code.
2005-04-20 00:58:25 +04:00
#define DEFAULT_PVSEGS_COLS "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,pvseg_start,pvseg_size"
reporting: Add devtypes command. Add internal devtypes reporting command to display built-in recognised block device types. (The output does not include any additional types added by a configuration file.) > lvm devtypes -o help Device Types Fields ------------------- devtype_all - All fields in this section. devtype_name - Name of Device Type exactly as it appears in /proc/devices. devtype_max_partitions - Maximum number of partitions. (How many device minor numbers get reserved for each device.) devtype_description - Description of Device Type. > lvm devtypes DevType MaxParts Description aoe 16 ATA over Ethernet ataraid 16 ATA Raid bcache 1 bcache block device cache blkext 1 Extended device partitions ...
2013-09-18 04:09:15 +04:00
#define DEFAULT_DEVTYPES_COLS "devtype_name,devtype_max_partitions,devtype_description"
report: add CMDLOG report type This is a preparation for new CMDLOG report type which is going to be used for reporting LVM command log. The new report type introduces several new fields (log_seq_num, log_type, log_context, log_object_type, log_object_group, log_object_id, object_name, log_message, log_errno, log_ret_code) as well as new configuration settings to set this report type (report/command_log_sort and report/command_log_cols lvm.conf settings). This patch also introduces internal report_cmdlog helper function which is a wrapper over dm_report_object to report command log via CMDLOG report type and which is going to be used throughout the code to report the log items.
2016-05-10 16:15:48 +03:00
#define DEFAULT_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"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
report: add vg_profile and lv_profile to report the profile attached to VG/LV vgs -o vg_profile ... lvs -o lv_profile ...
2013-07-02 16:34:52 +04:00
#define DEFAULT_LVS_COLS_VERB "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"
#define DEFAULT_VGS_COLS_VERB "vg_name,vg_attr,vg_extent_size,pv_count,lv_count,snap_count,vg_size,vg_free,vg_uuid,vg_profile"
Add dev_size column to pvs.
2004-08-11 17:15:05 +04:00
#define DEFAULT_PVS_COLS_VERB "pv_name,vg_name,pv_fmt,pv_attr,pv_size,pv_free,dev_size,pv_uuid"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_SEGS_COLS_VERB "lv_name,vg_name,lv_attr,seg_start,seg_size,stripes,segtype,stripesize,chunksize"
Append fields to report/pvsegs_cols_verbose. Permit LV segment fields with PV segment reports. Add seg_start_pe and seg_pe_ranges to reports.
2007-12-15 00:53:02 +03:00
#define DEFAULT_PVSEGS_COLS_VERB "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"
reporting: Add devtypes command. Add internal devtypes reporting command to display built-in recognised block device types. (The output does not include any additional types added by a configuration file.) > lvm devtypes -o help Device Types Fields ------------------- devtype_all - All fields in this section. devtype_name - Name of Device Type exactly as it appears in /proc/devices. devtype_max_partitions - Maximum number of partitions. (How many device minor numbers get reserved for each device.) devtype_description - Description of Device Type. > lvm devtypes DevType MaxParts Description aoe 16 ATA over Ethernet ataraid 16 ATA Raid bcache 1 bcache block device cache blkext 1 Extended device partitions ...
2013-09-18 04:09:15 +04:00
#define DEFAULT_DEVTYPES_COLS_VERB "devtype_name,devtype_max_partitions,devtype_description"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
commands: report: add lvm fullreport command lvm fullreport executes 5 subreports (vg, pv, lv, pvseg, seg) per each VG (and so taking one VG lock each time) within one command which makes it easier to produce full report about LVM entities. Since all 5 subreports for a VG are done under a VG lock, the output is more consistent mainly in cases where LVM entities may be changed in parallel.
2016-05-03 12:18:16 +03:00
#define DEFAULT_VGS_COLS_FULL "vg_all"
#define DEFAULT_PVS_COLS_FULL "pv_all"
#define DEFAULT_LVS_COLS_FULL "lv_all"
#define DEFAULT_PVSEGS_COLS_FULL "pvseg_all,pv_uuid,lv_uuid"
#define DEFAULT_SEGS_COLS_FULL "seg_all,lv_uuid"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
#define DEFAULT_LVS_SORT "vg_name,lv_name"
#define DEFAULT_VGS_SORT "vg_name"
#define DEFAULT_PVS_SORT "pv_name"
#define DEFAULT_SEGS_SORT "vg_name,lv_name,seg_start"
Initial pv_segment code.
2005-04-20 00:58:25 +04:00
#define DEFAULT_PVSEGS_SORT "pv_name,pvseg_start"
reporting: Add devtypes command. Add internal devtypes reporting command to display built-in recognised block device types. (The output does not include any additional types added by a configuration file.) > lvm devtypes -o help Device Types Fields ------------------- devtype_all - All fields in this section. devtype_name - Name of Device Type exactly as it appears in /proc/devices. devtype_max_partitions - Maximum number of partitions. (How many device minor numbers get reserved for each device.) devtype_description - Description of Device Type. > lvm devtypes DevType MaxParts Description aoe 16 ATA over Ethernet ataraid 16 ATA Raid bcache 1 bcache block device cache blkext 1 Extended device partitions ...
2013-09-18 04:09:15 +04:00
#define DEFAULT_DEVTYPES_SORT "devtype_name"
report: add CMDLOG report type This is a preparation for new CMDLOG report type which is going to be used for reporting LVM command log. The new report type introduces several new fields (log_seq_num, log_type, log_context, log_object_type, log_object_group, log_object_id, object_name, log_message, log_errno, log_ret_code) as well as new configuration settings to set this report type (report/command_log_sort and report/command_log_cols lvm.conf settings). This patch also introduces internal report_cmdlog helper function which is a wrapper over dm_report_object to report command log via CMDLOG report type and which is going to be used throughout the code to report the log items.
2016-05-10 16:15:48 +03:00
#define DEFAULT_COMMAND_LOG_SORT "log_seq_num"
New column-based reporting tools: lvs, pvs & vgs.
2002-12-12 23:55:49 +03:00
commands: report: add lvm fullreport command lvm fullreport executes 5 subreports (vg, pv, lv, pvseg, seg) per each VG (and so taking one VG lock each time) within one command which makes it easier to produce full report about LVM entities. Since all 5 subreports for a VG are done under a VG lock, the output is more consistent mainly in cases where LVM entities may be changed in parallel.
2016-05-03 12:18:16 +03:00
#define DEFAULT_VGS_SORT_FULL "vg_name"
#define DEFAULT_PVS_SORT_FULL "pv_name"
#define DEFAULT_LVS_SORT_FULL "vg_name,lv_name"
#define DEFAULT_PVSEGS_SORT_FULL "pv_uuid,pvseg_start"
#define DEFAULT_SEGS_SORT_FULL "lv_uuid,seg_start"
Use lvconvert --repair instead of vgreduce in mirror dmeventd DSO (mornfall) Introduce lvconvert --use_policies (mornfall)
2009-06-04 16:01:15 +04:00
#define DEFAULT_MIRROR_DEVICE_FAULT_POLICY "remove"
#define DEFAULT_MIRROR_LOG_FAULT_POLICY "allocate"
Implement automatic snapshot extension with dmeventd, and add two new options to lvm.conf in the activation section: 'snapshot_autoextend_threshold' and 'snapshot_autoextend_percent', that define how to handle automatic snapshot extension. The former defines when the snapshot should be extended: when its space usage exceeds this many percent. The latter defines how much extra space should be allocated for the snapshot, in percent of its current size.
2010-10-15 20:28:14 +04:00
#define DEFAULT_SNAPSHOT_AUTOEXTEND_THRESHOLD 100
#define DEFAULT_SNAPSHOT_AUTOEXTEND_PERCENT 20
Thin automatic policy based extension
2011-12-21 17:10:52 +04:00
#define DEFAULT_THIN_POOL_AUTOEXTEND_THRESHOLD 100
#define DEFAULT_THIN_POOL_AUTOEXTEND_PERCENT 20
dmeventd: lvm vdo support
2018-07-09 12:43:12 +03:00
#define DEFAULT_VDO_POOL_AUTOEXTEND_THRESHOLD 100
#define DEFAULT_VDO_POOL_AUTOEXTEND_PERCENT 20
Use lvconvert --repair instead of vgreduce in mirror dmeventd DSO (mornfall) Introduce lvconvert --use_policies (mornfall)
2009-06-04 16:01:15 +04:00
config: change scan_lvs default to 0 so that lvm does not scan LVs for PVs by default.
2019-02-20 22:30:46 +03:00
#define DEFAULT_SCAN_LVS 0
filter: add config setting to skip scanning LVs devices/scan_lvs (default 1) determines whether lvm will scan LVs for layered PVs. The lvm behavior has always been to scan LVs, but it's rare for LVs to have layered PVs, and much more common for there to be many LVs that substantially slow down scanning with no benefit. This is implemented in the usable filter, and has the same effect as listing all LVs in the global_filter.
2018-08-29 21:14:18 +03:00
add device hints to reduce scanning Save the list of PVs in /run/lvm/hints. These hints are used to reduce scanning in a number of commands to only the PVs on the system, or only the PVs in a requested VG (rather than all devices on the system.)
2018-12-07 23:35:22 +03:00
#define DEFAULT_HINTS "all"
io: increase the default io memory from 4 to 8 MiB This is the default bcache size that is created at the start of the command. It needs to be large enough to hold a single copy of metadata for a given VG, or the VG cannot be read or written (since the entire VG would not fit into available memory.) Increasing the default reduces the chances of anyone needing to increase the default to use their VG. The size can be set in lvm.conf global/io_memory_size; the lower limit is 4 MiB and the upper limit is 128 MiB.
2019-03-04 20:18:34 +03:00
#define DEFAULT_IO_MEMORY_SIZE_KB 8192
config: add new setting io_memory_size which defines the amount of memory that lvm will allocate for bcache. Increasing this setting is required if it is smaller than a single copy of VG metadata.
2019-03-01 22:55:59 +03:00
Additional MD component checking If udev info is missing for a device, (which would indicate if it's an MD component), then do an end-of-device read to check if a PV is an MD component. (This is skipped when using hints since we already know devs in hints are good.) A new config setting md_component_checks can be used to disable the additional end-of-device MD checks, or to always enable end-of-device MD checks. When both hints and udev info are disabled/unavailable, the end of PVs will now be scanned by default. If md devices with end-of-device superblocks are not being used, the extra I/O overhead can be avoided by setting md_component_checks="start".
2019-05-21 20:06:34 +03:00
#define DEFAULT_MD_COMPONENT_CHECKS "auto"
config: change default use_devicesfile to 1
2021-03-16 17:52:13 +03:00
#define DEFAULT_USE_DEVICES_FILE 1
device usage based on devices file The LVM devices file lists devices that lvm can use. The default file is /etc/lvm/devices/system.devices, and the lvmdevices(8) command is used to add or remove device entries. If the file does not exist, or if lvm.conf includes use_devicesfile=0, then lvm will not use a devices file. When the devices file is in use, the regex filter is not used, and the filter settings in lvm.conf or on the command line are ignored. LVM records devices in the devices file using hardware-specific IDs, such as the WWID, and attempts to use subsystem-specific IDs for virtual device types. These device IDs are also written in the VG metadata. When no hardware or virtual ID is available, lvm falls back using the unstable device name as the device ID. When devnames are used, lvm performs extra scanning to find devices if their devname changes, e.g. after reboot. When proper device IDs are used, an lvm command will not look at devices outside the devices file, but when devnames are used as a fallback, lvm will scan devices outside the devices file to locate PVs on renamed devices. A config setting search_for_devnames can be used to control the scanning for renamed devname entries. Related to the devices file, the new command option --devices <devnames> allows a list of devices to be specified for the command to use, overriding the devices file. The listed devices act as a sort of devices file in terms of limiting which devices lvm will see and use. Devices that are not listed will appear to be missing to the lvm command. Multiple devices files can be kept in /etc/lvm/devices, which allows lvm to be used with different sets of devices, e.g. system devices do not need to be exposed to a specific application, and the application can use lvm on its own set of devices that are not exposed to the system. The option --devicesfile <filename> is used to select the devices file to use with the command. Without the option set, the default system devices file is used. Setting --devicesfile "" causes lvm to not use a devices file. An existing, empty devices file means lvm will see no devices. The new command vgimportdevices adds PVs from a VG to the devices file and updates the VG metadata to include the device IDs. vgimportdevices -a will import all VGs into the system devices file. LVM commands run by dmeventd not use a devices file by default, and will look at all devices on the system. A devices file can be created for dmeventd (/etc/lvm/devices/dmeventd.devices) If this file exists, lvm commands run by dmeventd will use it. Internal implementaion: - device_ids_read - read the devices file . add struct dev_use (du) to cmd->use_devices for each devices file entry - dev_cache_scan - get /dev entries . add struct device (dev) to dev_cache for each device on the system - device_ids_match - match devices file entries to /dev entries . match each du on cmd->use_devices to a dev in dev_cache, using device ID . on match, set du->dev, dev->id, dev->flags MATCHED_USE_ID - label_scan - read lvm headers and metadata from devices . filters are applied, those that do not need data from the device . filter-deviceid skips devs without MATCHED_USE_ID, i.e. skips /dev entries that are not listed in the devices file . read lvm label from dev . filters are applied, those that use data from the device . read lvm metadata from dev . add info/vginfo structs for PVs/VGs (info is "lvmcache") - device_ids_find_renamed_devs - handle devices with unstable devname ID where devname changed . this step only needed when devs do not have proper device IDs, and their dev names change, e.g. after reboot sdb becomes sdc. . detect incorrect match because PVID in the devices file entry does not match the PVID found when the device was read above . undo incorrect match between du and dev above . search system devices for new location of PVID . update devices file with new devnames for PVIDs on renamed devices . label_scan the renamed devs - continue with command processing
2020-06-23 21:25:41 +03:00
#define DEFAULT_DEVICES_FILE "system.devices"
#define DEFAULT_SEARCH_FOR_DEVNAMES "auto"
devices: rework libudev usage related to config settings: obtain_device_info_from_udev (controls if lvm gets a list of devices from readdir /dev or from libudev) external_device_info_source (controls if lvm asks libudev for device information) . Make the obtain_device_list_from_udev setting affect only the choice of readdir /dev vs libudev. The setting no longer controls if udev is used for device type checks. . Change obtain_device_list_from_udev default to 0. This helps avoid boot timeouts due to slow libudev queries, avoids reported failures from udev_enumerate_scan_devices, and avoids delays from "device not initialized in udev database" errors. Even without errors, for a system booting with 1024 PVs, lvm2-pvscan times improve from about 100 sec to 15 sec, and the pvscan command from about 64 sec to about 4 sec. . For external_device_info_source="none", remove all libudev device info queries, and use only lvm native device info. . For external_device_info_source="udev", first check lvm native device info, then check libudev info. . Remove sleep/retry loop when attempting libudev queries for device info. udev info will simply be skipped if it's not immediately available. . Only set up a libdev connection if it will be used by obtain_device_list_from_udev/external_device_info_source. . For native multipath component detection, use /etc/multipath/wwids. If a device has a wwid matching an entry in the wwids file, then it's considered a multipath component. This is necessary to natively detect multipath components when the mpath device is not set up.
2021-06-09 01:12:09 +03:00
#define DEFAULT_WWIDS_FILE "/etc/multipath/wwids"
Refactoring.
2002-11-18 17:01:16 +03:00
#endif /* _LVM_DEFAULTS_H */
Copy Permalink