{ "content": [ { "type": "text", "text": "# lvm.conf (info)\n\n## NAME\n\nlvm.conf -- Configuration file for LVM2\n\n## SYNOPSIS\n\n/etc/lvm/lvm.conf\n\n## DESCRIPTION\n\nlvm.conf is loaded during the initialisation phase of lvm(8). This\nfile can in turn lead to other files being loaded - settings read in\nlater override earlier settings. File timestamps are checked between\ncommands and if any have changed, all the files are reloaded.\n\n## Sections\n\n- **NAME**\n- **SYNOPSIS**\n- **DESCRIPTION**\n- **SYNTAX**\n- **SETTINGS**\n- **FILES**\n- **SEE ALSO**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n" } ], "structuredContent": { "command": "lvm.conf", "section": "", "mode": "info", "summary": "lvm.conf -- Configuration file for LVM2", "synopsis": "/etc/lvm/lvm.conf", "tldr_summary": null, "tldr_examples": [], "tldr_source": null, "flags": [], "examples": [], "see_also": [ { "name": "lvm", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvm/8/json" }, { "name": "lvmconfig", "section": "8", "url": "https://www.chedong.com/phpMan.php/man/lvmconfig/8/json" }, { "name": "2.03.11", "section": "2", "url": "https://www.chedong.com/phpMan.php/man/2.03.11/2/json" }, { "name": "LVM.CONF", "section": "5", "url": "https://www.chedong.com/phpMan.php/man/LVM.CONF/5/json" } ], "section_outline": [ { "name": "NAME", "lines": 2, "subsections": [] }, { "name": "SYNOPSIS", "lines": 2, "subsections": [] }, { "name": "DESCRIPTION", "lines": 94, "subsections": [] }, { "name": "SYNTAX", "lines": 46, "subsections": [] }, { "name": "SETTINGS", "lines": 26, "subsections": [] }, { "name": "FILES", "lines": 8, "subsections": [] }, { "name": "SEE ALSO", "lines": 3, "subsections": [] } ], "sections": { "NAME": { "content": "lvm.conf -- Configuration file for LVM2\n", "subsections": [] }, "SYNOPSIS": { "content": "/etc/lvm/lvm.conf\n", "subsections": [] }, "DESCRIPTION": { "content": "lvm.conf is loaded during the initialisation phase of lvm(8). This\nfile can in turn lead to other files being loaded - settings read in\nlater override earlier settings. File timestamps are checked between\ncommands and if any have changed, all the files are reloaded.\n\nFor a description of each lvm.conf setting, run:\n\nlvmconfig --typeconfig default --withcomments --withspaces\n\nThe settings defined in lvm.conf can be overridden by any of these ex-\ntended configuration methods:\n\ndirect config override on command line\nThe --config ConfigurationString command line option takes the\nConfigurationString as direct string representation of the con-\nfiguration to override the existing configuration. The Configu-\nrationString is of exactly the same format as used in any LVM\nconfiguration file.\n\nprofile config\nA profile is a set of selected customizable configuration set-\ntings that are aimed to achieve a certain characteristics in\nvarious environments or uses. It's used to override existing\nconfiguration. Normally, the name of the profile should reflect\nthat environment or use.\n\nThere are two groups of profiles recognised: command profiles\nand metadata profiles.\n\nThe command profile is used to override selected configuration\nsettings at global LVM command level - it is applied at the very\nbeginning of LVM command execution and it is used throughout the\nwhole time of LVM command execution. The command profile is ap-\nplied by using the --commandprofile ProfileName command line op-\ntion that is recognised by all LVM2 commands.\n\nThe metadata profile is used to override selected configuration\nsettings at Volume Group/Logical Volume level - it is applied\nindependently for each Volume Group/Logical Volume that is being\nprocessed. As such, each Volume Group/Logical Volume can store\nthe profile name used in its metadata so next time the Volume\nGroup/Logical Volume is processed, the profile is applied auto-\nmatically. If Volume Group and any of its Logical Volumes have\ndifferent profiles defined, the profile defined for the Logical\nVolume is preferred. The metadata profile can be attached/de-\ntached by using the lvchange and vgchange commands and their\n--metadataprofile ProfileName and --detachprofile options or the\n--metadataprofile option during creation when using vgcreate or\nlvcreate command. The vgs and lvs reporting commands provide -o\nvgprofile and -o lvprofile output options to show the metadata\nprofile currently attached to a Volume Group or a Logical Vol-\nume.\n\nThe set of options allowed for command profiles is mutually ex-\nclusive when compared to the set of options allowed for metadata\nprofiles. The settings that belong to either of these two sets\ncan't be mixed together and LVM tools will reject such profiles.\n\nLVM itself provides a few predefined configuration profiles.\nUsers are allowed to add more profiles with different values if\nneeded. For this purpose, there's the commandprofiletem-\nplate.profile (for command profiles) and metadataprofiletem-\nplate.profile (for metadata profiles) which contain all settings\nthat are customizable by profiles of certain type. Users are en-\ncouraged to copy these template profiles and edit them as\nneeded. Alternatively, the lvmconfig --file --type profilable-command
or lvmconfig --file\n --type profilable-metadata
can\nbe used to generate a configuration with profilable settings in\neither of the type for given section and save it to new Profile-\nName.profile (if the section is not specified, all profilable\nsettings are reported).\n\nThe profiles are stored in /etc/lvm/profile directory by de-\nfault. This location can be changed by using the config/pro-\nfiledir setting. Each profile configuration is stored in Pro-\nfileName.profile file in the profile directory. When referencing\nthe profile, the .profile suffix is left out.\n\ntag config\nSee tags configuration setting description below.\n\nWhen several configuration methods are used at the same time and when\nLVM looks for the value of a particular setting, it traverses this con-\nfig cascade from left to right:\n\ndirect config override on command line-> command profile config-> meta-\ndata profile config-> tag config-> lvmlocal.conf-> lvm.conf\n\nNo part of this cascade is compulsory. If there's no setting value\nfound at the end of the cascade, a default value is used for that set-\nting. Use lvmconfig to check what settings are in use and what the de-\nfault values are.\n", "subsections": [] }, "SYNTAX": { "content": "This section describes the configuration file syntax.\n\nWhitespace is not significant unless it is within quotes. This pro-\nvides a wide choice of acceptable indentation styles. Comments begin\nwith # and continue to the end of the line. They are treated as white-\nspace.\n\nHere is an informal grammar:\n\nfile = value*\nA configuration file consists of a set of values.\n\nvalue = section | assignment\nA value can either be a new section, or an assignment.\n\nsection = identifier '{' value* '}'\nA section groups associated values together. If the same section\nis encountered multiple times, the contents of all instances are\nconcatenated together in the order of appearance.\nIt is denoted by a name and delimited by curly brackets.\ne.g. backup {\n...\n}\n\nassignment = identifier '=' ( array | type )\nAn assignment associates a type with an identifier. If the iden-\ntifier contains forward slashes, those are interpreted as path\ndelimiters. The statement section/key = value is equivalent to\nsection { key = value }. If multiple instances of the same key\nare encountered, only the last value is used (and a warning is\nissued).\ne.g. level = 7\n\narray = '[' ( type ',')* type ']' | '[' ']'\nInhomogeneous arrays are supported.\nElements must be separated by commas.\nAn empty array is acceptable.\n\ntype = integer | float | string\ninteger = [0-9]*\nfloat = [0-9]*'.'[0-9]*\nstring = '\"'.*'\"'\n\nStrings with spaces must be enclosed in double quotes, single\nwords that start with a letter can be left unquoted.\n", "subsections": [] }, "SETTINGS": { "content": "The lvmconfig command prints the LVM configuration settings in various\nways. See the man page lvmconfig(8).\n\nCommand to print a list of all possible config settings, with their de-\nfault values:\nlvmconfig --type default\n\nCommand to print a list of all possible config settings, with their de-\nfault values, and a full description of each as a comment:\nlvmconfig --type default --withcomments\n\nCommand to print a list of all possible config settings, with their\ncurrent values (configured, non-default values are shown):\nlvmconfig --type current\n\nCommand to print all config settings that have been configured with a\ndifferent value than the default (configured, non-default values are\nshown):\nlvmconfig --type diff\n\nCommand to print a single config setting, with its default value, and a\nfull description, where \"Section\" refers to the config section, e.g.\nglobal, and \"Setting\" refers to the name of the specific setting, e.g.\numask:\nlvmconfig --type default --withcomments Section/Setting\n", "subsections": [] }, "FILES": { "content": "/etc/lvm/lvm.conf\n/etc/lvm/lvmlocal.conf\n/etc/lvm/archive\n/etc/lvm/backup\n/etc/lvm/cache/.cache\n/run/lock/lvm\n/etc/lvm/profile\n", "subsections": [] }, "SEE ALSO": { "content": "lvm(8) lvmconfig(8)\n\nRed Hat, Inc. LVM TOOLS 2.03.11(2) (2021-01-08) LVM.CONF(5)", "subsections": [] } } } }