info > lvm.conf(5)

man perldoc info pydoc3 ri search

Not found locally for lvm.conf. Try Google search

🔖 NAME

lvm.conf — Configuration file for LVM2

🚀 Quick Reference

Use Case	Command	Description
📋 Print all default settings with comments	lvmconfig --type default --withcomments	View complete configuration with descriptions
⚙️ Print current active settings (non-default highlighted)	lvmconfig --type current	See what's actually configured
🔍 Show differences from defaults	lvmconfig --type diff	Spot customized settings
🎯 Check a specific setting	lvmconfig --type default --withcomments Section/Setting	Get description and default for e.g. global/umask
📁 Use a command profile	--commandprofile ProfileName	Override config at LVM command level
📦 Attach metadata profile to VG/LV	vgchange --metadataprofile ProfileName	Persistent per-VG/LV config override

📋 SYNOPSIS

/etc/lvm/lvm.conf

📝 DESCRIPTION

lvm.conf is loaded during the initialisation phase of lvm(8). This file can in turn lead to other files being loaded — settings read in later override earlier settings. File timestamps are checked between commands and if any have changed, all the files are reloaded.

For a description of each lvm.conf setting, run:

lvmconfig --typeconfig default --withcomments --withspaces

The settings defined in lvm.conf can be overridden by any of these extended configuration methods:

🔧 Direct config override on command line

The --config ConfigurationString 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.

📁 Profile config

A profile is a set of selected customizable configuration settings that are aimed to achieve a certain characteristics in various environments or uses. It's used to override existing configuration. Normally, the name of the profile should reflect that environment or use.

There are two groups of profiles recognised: command profiles and metadata profiles.

• 📋 Command profile — applied at the very beginning of LVM command execution, used throughout the whole time. Applied via --commandprofile ProfileName option.
• 📦 Metadata profile — applied independently for each VG/LV being processed. Stored in metadata so next time it's applied automatically. Attached/detached via lvchange/vgchange with --metadataprofile or --detachprofile. Also available during creation with vgcreate/lvcreate.

The set of options allowed for command profiles is mutually exclusive compared to metadata profiles. LVM tools will reject mixed profiles.

LVM provides a few predefined configuration profiles. Users can add more by copying command_profile_template.profile or metadata_profile_template.profile from /etc/lvm/profile/. Alternatively, generate a profile file with:

lvmconfig --file <ProfileName.profile> --type profilable-command <section>
lvmconfig --file <ProfileName.profile> --type profilable-metadata <section>

Profiles are stored in /etc/lvm/profile by default (configurable via config/profile_dir). When referencing a profile, the .profile suffix is omitted.

🏷️ Tag config

See the tags configuration setting description below.

When several configuration methods are used simultaneously, LVM traverses the config cascade left to right:

direct config override → command profile → metadata profile → tag config → lvmlocal.conf → lvm.conf

No part of this cascade is compulsory. If no setting value is found, a default value is used. Use lvmconfig to check what settings are in use and what the defaults are.

🔧 SYNTAX

This section describes the configuration file syntax.

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.

Here is an informal grammar:

file = value*
A configuration file consists of a set of values.

value = section | assignment
A value can either be a new section, or an assignment.

section = identifier '{' value* '}'
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.
It is denoted by a name and delimited by curly brackets.
e.g. backup {
           ...
      }

assignment = identifier '=' ( array | type )
An assignment associates a type with an identifier. If the identifier contains forward slashes, those are interpreted as path delimiters. The statement section/key = value is equivalent to section { key = value }. If multiple instances of the same key are encountered, only the last value is used (and a warning is issued).
e.g. level = 7

array =  '[' ( type ',')* type ']' | '[' ']'
Inhomogeneous arrays are supported.
Elements must be separated by commas.
An empty array is acceptable.

type = integer | float | string
integer = [0-9]*
float = [0-9]*'.'[0-9]*
string = '"'.*'"'

Strings with spaces must be enclosed in double quotes, single words that start with a letter can be left unquoted.

⚙️ SETTINGS

The lvmconfig command prints the LVM configuration settings in various ways. See the man page lvmconfig(8).

• 📋 Print a list of all possible config settings with their default values:

  lvmconfig --type default

• 📋 Print with full description as comments:

  lvmconfig --type default --withcomments

• ⚙️ Print current active values (non-default shown):

  lvmconfig --type current

• 🔍 Print only settings that differ from defaults:

  lvmconfig --type diff

• 🎯 Print a single config setting (e.g., global/umask):

  lvmconfig --type default --withcomments Section/Setting

📁 FILES

/etc/lvm/lvm.conf
/etc/lvm/lvmlocal.conf
/etc/lvm/archive
/etc/lvm/backup
/etc/lvm/cache/.cache
/run/lock/lvm
/etc/lvm/profile

🔗 SEE ALSO

lvm(8), lvmconfig(8)

Red Hat, Inc.   LVM TOOLS 2.03.11(2) (2021-01-08)   LVM.CONF(5)

🔖 NAME 🚀 Quick Reference 📋 SYNOPSIS 📝 DESCRIPTION 🔧 SYNTAX ⚙️ SETTINGS 📁 FILES 🔗 SEE ALSO