NAME<\/a> lvm.conf \u2014 Configuration file for LVM2<\/p>\n \/etc\/lvm\/lvm.conf<\/b><\/p>\n lvm.conf<\/b> is loaded during the initialisation phase of lvm<\/b>(8). This file can in turn lead to other files being loaded \u2212 settings read in later override earlier settings. File timestamps are checked between commands and if any have changed, all the files are reloaded.<\/p>\n For a description of each lvm.conf setting, run:<\/p>\n lvmconfig \u2212\u2212typeconfig default \u2212\u2212withcomments \u2212\u2212withspaces<\/b><\/p>\n The settings defined in lvm.conf can be overridden by any of these extended configuration methods: The \u2212\u2212config ConfigurationString<\/b> command line option takes the ConfigurationString as direct string representation of the configuration to override the existing configuration. The ConfigurationString is of exactly the same format as used in any LVM configuration file.<\/p>\n profile config<\/b><\/p>\n A profile is a set of selected customizable configuration settings that are aimed to achieve a certain characteristics in various environments or uses. It\u2019s used to override existing configuration. Normally, the name of the profile should reflect that environment or use.<\/p>\n There are two groups of profiles recognised: command profiles<\/b> and metadata profiles<\/b>.<\/p>\n The command profile<\/b> is used to override selected configuration settings at global LVM command level \u2212 it is applied at the very beginning of LVM command execution and it is used throughout the whole time of LVM command execution. The command profile is applied by using the \u2212\u2212commandprofile ProfileName<\/b> command line option that is recognised by all LVM2 commands.<\/p>\n The metadata profile<\/b> is used to override selected configuration settings at Volume Group\/Logical Volume level \u2212 it is applied independently for each Volume Group\/Logical Volume that is being processed. As such, each Volume Group\/Logical Volume can store the profile name used in its metadata so next time the Volume Group\/Logical Volume is processed, the profile is applied automatically. If Volume Group and any of its Logical Volumes have different profiles defined, the profile defined for the Logical Volume is preferred. The metadata profile can be attached\/detached by using the lvchange<\/b> and vgchange<\/b> commands and their \u2212\u2212metadataprofile ProfileName<\/b> and \u2212\u2212detachprofile<\/b> options or the \u2212\u2212metadataprofile<\/b> option during creation when using vgcreate<\/b> or lvcreate<\/b> command. The vgs<\/b> and lvs<\/b> reporting commands provide \u2212o vg_profile<\/b> and \u2212o lv_profile<\/b> output options to show the metadata profile currently attached to a Volume Group or a Logical Volume.<\/p>\n The set of options allowed for command profiles is mutually exclusive when compared to the set of options allowed for metadata profiles. The settings that belong to either of these two sets can\u2019t be mixed together and LVM tools will reject such profiles.<\/p>\n LVM itself provides a few predefined configuration profiles. Users are allowed to add more profiles with different values if needed. For this purpose, there\u2019s the command_profile_template.profile<\/b> (for command profiles) and metadata_profile_template.profile<\/b> (for metadata profiles) which contain all settings that are customizable by profiles of certain type. Users are encouraged to copy these template profiles and edit them as needed. Alternatively, the lvmconfig \u2212\u2212file The profiles are stored in \/etc\/lvm\/profile directory by default. This location can be changed by using the config\/profile_dir<\/b> setting. Each profile configuration is stored in ProfileName.profile<\/b> file in the profile directory. When referencing the profile, the .profile<\/b> suffix is left out.<\/p>\n tag config<\/b><\/p>\n See tags<\/b> configuration setting description below.<\/p>\n When several configuration methods are used at the same time and when LVM looks for the value of a particular setting, it traverses this config cascade<\/b> from left to right:<\/p>\n direct config override on command line<\/b>\u2212> command profile config<\/b>\u2212> metadata profile config<\/b>\u2212> tag config<\/b>\u2212> lvmlocal.conf\u2212> lvm.conf<\/b><\/p>\n No part of this cascade is compulsory. If there\u2019s no setting value found at the end of the cascade, a default value is used for that setting. Use lvmconfig to check what settings are in use and what the default values are.<\/b><\/p>\n This section describes the configuration file syntax.<\/p>\n Whitespace is not significant unless it is within quotes. This provides a wide choice of acceptable indentation styles. Comments begin with # and continue to the end of the line. They are treated as whitespace.<\/p>\n Here is an informal grammar: A configuration file consists of a set of values.<\/p>\n value<\/b> = section<\/b> | assignment<\/b><\/p>\n A value can either be a new section, or an assignment.<\/p>\n section<\/b> = identifier<\/b> \u2019{<\/b>\u2019 value<\/b>* \u2019}<\/b>\u2019<\/p>\n A section groups associated values together. If the same section is encountered multiple times, the contents of all instances are concatenated together in the order of appearance.
SYNOPSIS<\/a>
DESCRIPTION<\/a>
SYNTAX<\/a>
SETTINGS<\/a>
FILES<\/a>
SEE ALSO<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
direct config override on command line<\/b><\/p>\nSYNTAX <\/a> <\/h2>\n
file<\/b> = value<\/b>*<\/p>\n
It is denoted by a name and delimited by curly brackets.<\/p>\n