blob: c8e6484eb9dce9f3817b6c42e42baeb478c71481 [file] [log] [blame]
.TH LVM 8 "LVM TOOLS #VERSION#" "Sistina Software UK" \" -*- nroff -*-
lvm \(em LVM2 tools
.B lvm
[command | file]
lvm provides the command-line tools for LVM2. A separate
manual page describes each command in detail.
If \fBlvm\fP is invoked with no arguments it presents a readline prompt
(assuming it was compiled with readline support).
LVM commands may be entered interactively at this prompt with
readline facilities including history and command name and option
completion. Refer to \fBreadline\fP(3) for details.
If \fBlvm\fP is invoked with argv[0] set to the name of a specific
LVM command (for example by using a hard or soft link) it acts as
that command.
On invocation, \fBlvm\fP requires that only the standard file descriptors
stdin, stdout and stderr are available. If others are found, they
get closed and messages are issued warning about the leak.
This warning can be suppressed by setting the environment variable
Where commands take VG or LV names as arguments, the full path name is
optional. An LV called "lvol0" in a VG called "vg0" can be specified
as "vg0/lvol0". Where a list of VGs is required but is left empty,
a list of all VGs will be substituted. Where a list of LVs is required
but a VG is given, a list of all the LVs in that VG will be substituted.
So \fBlvdisplay vg0\fP will display all the LVs in "vg0".
Tags can also be used - see \fB\-\-addtag\fP below.
One advantage of using the built-in shell is that configuration
information gets cached internally between commands.
A file containing a simple script with one command per line
can also be given on the command line. The script can also be
executed directly if the first line is #! followed by the absolute
path of \fBlvm\fP.
The following commands are built into lvm without links normally
being created in the filesystem for them.
\fBconfig\fP \(em The same as \fBlvmconfig\fP(8) below.
\fBdevtypes\fP \(em Display the recognised built-in block device types.
\fBdumpconfig\fP \(em The same as \fBlvmconfig\fP(8) below.
\fBformats\fP \(em Display recognised metadata formats.
\fBhelp\fP \(em Display the help text.
\fBlvpoll\fP \(em Internal command used by lvmpolld to complete some Logical Volume operations.
\fBpvdata\fP \(em Not implemented in LVM2.
\fBsegtypes\fP \(em Display recognised Logical Volume segment types.
\fBsystemid\fP \(em Display the system ID, if any, currently set on this host.
\fBtags\fP \(em Display any tags defined on this host.
\fBversion\fP \(em Display version information.
The following commands implement the core LVM functionality.
\fBpvchange\fP \(em Change attributes of a Physical Volume.
\fBpvck\fP \(em Check Physical Volume metadata.
\fBpvcreate\fP \(em Initialize a disk or partition for use by LVM.
\fBpvdisplay\fP \(em Display attributes of a Physical Volume.
\fBpvmove\fP \(em Move Physical Extents.
\fBpvremove\fP \(em Remove a Physical Volume.
\fBpvresize\fP \(em Resize a disk or partition in use by LVM2.
\fBpvs\fP \(em Report information about Physical Volumes.
\fBpvscan\fP \(em Scan all disks for Physical Volumes.
\fBvgcfgbackup\fP \(em Backup Volume Group descriptor area.
\fBvgcfgrestore\fP \(em Restore Volume Group descriptor area.
\fBvgchange\fP \(em Change attributes of a Volume Group.
\fBvgck\fP \(em Check Volume Group metadata.
\fBvgconvert\fP \(em Convert Volume Group metadata format.
\fBvgcreate\fP \(em Create a Volume Group.
\fBvgdisplay\fP \(em Display attributes of Volume Groups.
\fBvgexport\fP \(em Make volume Groups unknown to the system.
\fBvgextend\fP \(em Add Physical Volumes to a Volume Group.
\fBvgimport\fP \(em Make exported Volume Groups known to the system.
\fBvgimportclone\fP \(em Import and rename duplicated Volume Group (e.g. a hardware snapshot).
\fBvgmerge\fP \(em Merge two Volume Groups.
\fBvgmknodes\fP \(em Recreate Volume Group directory and Logical Volume special files
\fBvgreduce\fP \(em Reduce a Volume Group by removing one or more
Physical Volumes.
\fBvgremove\fP \(em Remove a Volume Group.
\fBvgrename\fP \(em Rename a Volume Group.
\fBvgs\fP \(em Report information about Volume Groups.
\fBvgscan\fP \(em Scan all disks for Volume Groups and rebuild caches.
\fBvgsplit\fP \(em Split a Volume Group into two, moving any logical
volumes from one Volume Group to another by moving entire Physical
\fBlvchange\fP \(em Change attributes of a Logical Volume.
\fBlvconvert\fP \(em Convert a Logical Volume from linear to mirror or snapshot.
\fBlvcreate\fP \(em Create a Logical Volume in an existing Volume Group.
\fBlvdisplay\fP \(em Display attributes of a Logical Volume.
\fBlvextend\fP \(em Extend the size of a Logical Volume.
\fBlvmchange\fP \(em Change attributes of the Logical Volume Manager.
\fBlvmconfig\fP \(em Display the configuration information after
loading \fBlvm.conf\fP(5) and any other configuration files.
\fBlvmdiskscan\fP \(em Scan for all devices visible to LVM2.
\fBlvmdump\fP \(em Create lvm2 information dumps for diagnostic purposes.
\fBlvreduce\fP \(em Reduce the size of a Logical Volume.
\fBlvremove\fP \(em Remove a Logical Volume.
\fBlvrename\fP \(em Rename a Logical Volume.
\fBlvresize\fP \(em Resize a Logical Volume.
\fBlvs\fP \(em Report information about Logical Volumes.
\fBlvscan\fP \(em Scan (all disks) for Logical Volumes.
The following commands are not implemented in LVM2 but might be in the future: lvmsadc, lvmsar, pvdata.
The following options are available for many of the commands.
They are implemented generically and documented here rather
than repeated on individual manual pages.
Additional hyphens within option names are ignored. For example,
\-\-readonly and \-\-read\-only are both accepted.
.BR \-h ", " \-? ", " \-\-help
Display the help text.
.B \-\-version
Display version information.
.BR \-v ", " \-\-verbose
Set verbose level. Repeat from 1 to 3 times to increase the detail
of messages sent to stdout and stderr. Overrides config file setting.
.BR \-d ", " \-\-debug
Set debug level. Repeat from 1 to 6 times to increase the detail of
messages sent to the log file and/or syslog (if configured).
Overrides config file setting.
.BR \-q ", " \-\-quiet
Suppress output and log messages.
Overrides \fB\-d\fP and \fB\-v\fP.
Repeat once to also suppress any prompts with answer 'no'.
.BR \-\-yes
Don't prompt for confirmation interactively but instead always assume the
answer is 'yes'. Take great care if you use this!
.BR \-t ", " \-\-test
Run in test mode. Commands will not update metadata.
This is implemented by disabling all metadata writing but nevertheless
returning success to the calling function. This may lead to unusual
error messages in multi-stage operations if a tool relies on reading
back metadata it believes has changed but hasn't.
.BR \-\-driverloaded " {" \fIy | \fIn }
Whether or not the device-mapper kernel driver is loaded.
If you set this to \fIn\fP, no attempt will be made to contact the driver.
.BR \-A ", " \-\-autobackup " {" \fIy | \fIn }
Whether or not to metadata should be backed up automatically after a change.
You are strongly advised not to disable this!
See \fBvgcfgbackup\fP(8).
.BR \-P ", " \-\-partial
When set, the tools will do their best to provide access to Volume Groups
that are only partially available (one or more Physical Volumes belonging
to the Volume Group are missing from the system). Where part of a logical
volume is missing, \fB/dev/ioerror\fP will be substituted, and you could use
\fBdmsetup\fP(8) to set this up to return I/O errors when accessed,
or create it as a large block device of nulls. Metadata may not be
changed with this option. To insert a replacement Physical Volume
of the same or large size use \fBpvcreate \-u\fP to set the uuid to
match the original followed by \fBvgcfgrestore\fP(8).
.BR \-S ", " \-\-select " " \fISelection
For reporting commands, display only rows that match selection criteria.
All rows are displayed with the additional "selected" column (\fB-o selected\fP)
showing 1 if the row matches the Selection and 0 otherwise. For non-reporting
commands which process LVM entities, the selection can be used to match items
to process. See \fBSELECTION CRITERIA\fP section of this man page for more
information about the way the selection criteria are constructed.
.BR \-M ", " \-\-metadatatype " " \fIType
Specifies which type of on-disk metadata to use, such as \fIlvm1\fP
or \fIlvm2\fP, which can be abbreviated to \fI1\fP or \fI2\fP respectively.
The default (\fIlvm2\fP) can be changed by setting \fBformat\fP
in the \fBglobal\fP section of the config file.
.B \-\-ignorelockingfailure
This lets you proceed with read-only metadata operations such as
\fBlvchange \-ay\fP and \fBvgchange \-ay\fP even if the locking module fails.
One use for this is in a system init script if the lock directory
is mounted read-only when the script runs.
.B \-\-ignoreskippedcluster
Use to avoid exiting with an non-zero status code if the command is run
without clustered locking and some clustered Volume Groups have to be
skipped over.
.B \-\-readonly
Run the command in a special read-only mode which will read on-disk
metadata without needing to take any locks. This can be used to peek
inside metadata used by a virtual machine image while the virtual
machine is running.
It can also be used to peek inside the metadata of clustered Volume
Groups when clustered locking is not configured or running. No attempt
will be made to communicate with the device-mapper kernel driver, so
this option is unable to report whether or not Logical Volumes are
actually in use.
.B \-\-foreign
Cause the command to access foreign VGs, that would otherwise be skipped.
It can be used to report or display a VG that is owned by another host.
This option can cause a command to perform poorly because lvmetad caching
is not used and metadata is read from disks.
.B \-\-shared
Cause the command to access shared VGs, that would otherwise be skipped
when lvmlockd is not being used. It can be used to report or display a
lockd VG without locking.
.B \-\-addtag \fITag
Add the tag \fITag\fP to a PV, VG or LV.
Supply this argument multiple times to add more than one tag at once.
A tag is a word that can be used to group LVM2 objects of the same type
Tags can be given on the command line in place of PV, VG or LV
arguments. Tags should be prefixed with @ to avoid ambiguity.
Each tag is expanded by replacing it with all objects possessing
that tag which are of the type expected by its position on the command line.
PVs can only possess tags while they are part of a Volume Group:
PV tags are discarded if the PV is removed from the VG.
As an example, you could tag some LVs as \fBdatabase\fP and others
as \fBuserdata\fP and then activate the database ones
with \fBlvchange \-ay @database\fP.
Objects can possess multiple tags simultaneously.
Only the new LVM2 metadata format supports tagging: objects using the
LVM1 metadata format cannot be tagged because the on-disk format does not
support it.
Characters allowed in tags are:
.B A-Z a-z 0-9 _ + . -
and as of version 2.02.78 the following characters are also accepted:
.B / = ! : # &
.B \-\-deltag \fITag
Delete the tag \fITag\fP from a PV, VG or LV, if it's present.
Supply this argument multiple times to remove more than one tag at once.
.IR \fB\-\-alloc \ { anywhere | contiguous | cling | inherit | normal }
Selects the allocation policy when a command needs to allocate
Physical Extents from the Volume Group.
Each Volume Group and Logical Volume has an allocation policy defined.
The default for a Volume Group is \fInormal\fP which applies
common-sense rules such as not placing parallel stripes on the same
Physical Volume. The default for a Logical Volume is \fIinherit\fP
which applies the same policy as for the Volume Group. These policies can
be changed using \fBlvchange\fP(8) and \fBvgchange\fP(8) or overridden
on the command line of any command that performs allocation.
The \fIcontiguous\fP policy requires that new Physical Extents be placed adjacent
to existing Physical Extents.
The \fIcling\fP policy places new Physical Extents on the same Physical
Volume as existing Physical Extents in the same stripe of the Logical Volume.
If there are sufficient free Physical Extents to satisfy
an allocation request but \fInormal\fP doesn't use them,
\fIanywhere\fP will - even if that reduces performance by
placing two stripes on the same Physical Volume.
.IR \fB\-\-commandprofile " " \fIProfileName
Selects the command configuration profile to use when processing an LVM command.
See also \fBlvm.conf\fP(5) for more information about \fBcommand profile config\fP and
the way it fits with other LVM configuration methods. Using \fB\-\-commandprofile\fP
option overrides any command profile specified via \fBLVM_COMMAND_PROFILE\fP
environment variable.
.IR \fB\-\-metadataprofile " " \fIProfileName
Selects the metadata configuration profile to use when processing an LVM command.
When using metadata profile during Volume Group or Logical Volume creation,
the metadata profile name is saved in metadata. When such Volume Group or Logical
Volume is processed next time, the metadata profile is automatically applied
and the use of \-\-metadataprofile option is not necessary. See also
\fBlvm.conf\fP(5) for more information about \fBmetadata profile config\fP and the
way it fits with other LVM configuration methods.
.IR \fB\-\-profile " " \fIProfileName
A short form of \fB\-\-metadataprofile\fP for \fBvgcreate\fP, \fBlvcreate\fP,
\fBvgchange\fP and \fBlvchange\fP command and a short form of \fB\-\-commandprofile\fP
for any other command (with the exception of \fBlvmconfig\fP command where the
\-\-profile has special meaning, see \fBlvmconfig\fP(8) for more information).
.IR \fB\-\-config " " \fIConfigurationString
Uses 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. See \fBlvm.conf\fP(5)
for more information about \fBdirect config override on command line\fP and the
way it fits with other LVM configuration methods.
The valid characters for VG and LV names are:
.B a-z A-Z 0-9 + _ . -
VG and LV names cannot begin with a hyphen.
There are also various reserved names that are used internally by lvm that can not be used as LV or VG names.
A VG cannot be called anything that exists in /dev/ at the time of creation, nor can it be called '.' or '..'.
An LV cannot be called '.', '..', 'snapshot' or 'pvmove'. The LV name may also not contain any of the following
strings: '_cdata', '_cmeta', '_corig', '_mlog', '_mimage', '_pmspare', '_rimage', '_rlog', '_tdata' or '_tmeta'.
A directory bearing the name of each Volume Group is created under /dev when any of its Logical Volumes are activated.
Each active Logical Volume is accessible from this directory as a symbolic link leading to a device node.
Links or nodes in /dev/mapper are intended only for internal use and the precise format and escaping might change between releases and distributions.
Other software and scripts should use the
/dev/VolumeGroupName/LogicalVolumeName format to reduce the chance of needing
amendment when the software is updated. Should you need to process the node
names in /dev/mapper, you may use \fBdmsetup splitname\fP to separate out the
original VG, LV and internal layer names.
When an operation needs to allocate Physical Extents for one or more
Logical Volumes, the tools proceed as follows:
First of all, they generate the complete set of unallocated Physical Extents
in the Volume Group. If any ranges of Physical Extents are supplied at
the end of the command line, only unallocated Physical Extents within
those ranges on the specified Physical Volumes are considered.
Then they try each allocation policy in turn, starting with the strictest
policy (\fIcontiguous\fP) and ending with the allocation policy specified
using \fB\-\-alloc\fP or set as the default for the particular Logical
Volume or Volume Group concerned. For each policy, working from the
lowest-numbered Logical Extent of the empty Logical Volume space that
needs to be filled, they allocate as much space as possible according to
the restrictions imposed by the policy. If more space is needed,
they move on to the next policy.
The restrictions are as follows:
\fIContiguous\fP requires that the physical location of any Logical
Extent that is not the first Logical Extent of a Logical Volume is
adjacent to the physical location of the Logical Extent immediately
preceding it.
\fICling\fP requires that the Physical Volume used for any Logical
Extent to be added to an existing Logical Volume is already in use by at
least one Logical Extent earlier in that Logical Volume. If the
configuration parameter allocation/cling_tag_list is defined, then two
Physical Volumes are considered to match if any of the listed tags is
present on both Physical Volumes. This allows groups of Physical
Volumes with similar properties (such as their physical location) to be
tagged and treated as equivalent for allocation purposes.
When a Logical Volume is striped or mirrored, the above restrictions are
applied independently to each stripe or mirror image (leg) that needs
\fINormal\fP will not choose a Physical Extent that shares the same Physical
Volume as a Logical Extent already allocated to a parallel Logical
Volume (i.e. a different stripe or mirror image/leg) at the same offset
within that parallel Logical Volume.
When allocating a mirror log at the same time as Logical Volumes to hold
the mirror data, Normal will first try to select different Physical
Volumes for the log and the data. If that's not possible and the
allocation/mirror_logs_require_separate_pvs configuration parameter is
set to 0, it will then allow the log to share Physical Volume(s) with
part of the data.
When allocating thin pool metadata, similar considerations to those of a
mirror log in the last paragraph apply based on the value of the
allocation/thin_pool_metadata_require_separate_pvs configuration
If you rely upon any layout behaviour beyond that documented here, be
aware that it might change in future versions of the code.
For example, if you supply on the command line two empty Physical
Volumes that have an identical number of free Physical Extents available for
allocation, the current code considers using each of them in the order
they are listed, but there is no guarantee that future releases will
maintain that property. If it is important to obtain a specific layout
for a particular Logical Volume, then you should build it up through a
sequence of \fBlvcreate\fP(8) and \fBlvconvert\fP(8) steps such that the
restrictions described above applied to each step leave the tools no
discretion over the layout.
To view the way the allocation process currently works in any specific
case, read the debug logging output, for example by adding \fB\-vvvv\fP to
a command.
Some logical volume types are simple to create and can be done with a
single \fBlvcreate\fP(8) command. The linear and striped logical
volume types are an example of this. Other logical volume types may
require more than one command to create. The cache (\fBlvmcache\fP(7))
and thin provisioning (\fBlvmthin\fP(7)) types are examples of this.
The selection criteria are a set of \fBstatements\fP combined by \fBlogical
and grouping operators\fP. The \fBstatement\fP consists of \fBcolumn\fP
name for which a set of valid \fBvalues\fP is defined using
\fBcomparison operators\fP. For complete list of column names (fields)
that can be used in selection, see the output of \fB<lvm reporting command> -S help\fP.
\fBComparison operators\fP (cmp_op):
\fB=~\fP \(em Matching regular expression.
\fB!~\fP \(em Not matching regular expression.
\fB=\fP \(em Equal to.
\fB!=\fP \(em Not equal to.
\fB>=\fP \(em Greater than or equal to.
\fB>\fP \(em Greater than
\fB<=\fP \(em Less than or equal to.
\fB<\fP \(em Less than.
\fBBinary logical operators\fP (cmp_log):
\fB&&\fP \(em All fields must match
\fB,\fP \(em All fields must match
\fB||\fP \(em At least one field must match
\fB#\fP \(em At least one field must match
\fBUnary logical operators\fP:
\fB!\fP \(em Logical negation
\fBGrouping operators\fP:
\fB(\fP \(em Left parenthesis
\fB)\fP \(em Right parenthesis
\fB[\fP \(em List start
\fB]\fP \(em List end
\fB{\fP \(em List subset start
\fB}\fP \(em List subset end
\fBInformal grammar specification\fP:
.BR STATEMENT " = " column " cmp_op " VALUE " | " STATEMENT " log_op " STATEMENT " | " (STATEMENT) " | " !(STATEMENT)
.BR VALUE " = " [VALUE " log_op " VALUE]
For list-based types: string list. Matches strictly. The log_op must always be of one type within the whole list value.
.BR VALUE " = " {VALUE " log_op " VALUE}
For list-based types: string list. Matches a subset. The log_op must always be of one type within the whole list value.
.BR VALUE " = " value
For scalar types: number (integer), size (floating point number with size unit suffix), percent (floating point number with or without % suffix), string.
All tools return a status code of zero on success or non-zero on failure.
Directory containing \fI.lvm_history\fP if the internal readline
shell is invoked.
Name of default command profile to use for LVM commands. This profile
is overriden by direct use of \fB\-\-commandprofile\fP command line option.
Directory containing \fBlvm.conf\fP(5) and other LVM system files.
Defaults to "#DEFAULT_SYS_DIR#".
Suppress warnings about unexpected file descriptors passed into LVM.
The Volume Group name that is assumed for
any reference to a Logical Volume that doesn't specify a path.
Not set by default.
Path to the file that stores the lvmetad process ID.
Path to the socket used to communicate with lvmetad.
Path to the file that stores the lvmpolld process ID.
Path to the socket used to communicate with lvmpolld..
A string of up to 32 letters appended to the log filename and
followed by the process ID and a timestamp. When set, each process logs to a
separate file.
The status anticipated when the process exits. Use ">N" to match any
status greater than N. If the actual exit status matches and a log
file got produced, it is deleted.
automated test scripts to discard uninteresting log data.
Used to suppress warning messages when the configured locking is known
to be unavailable.
Abort processing if the code detects a non-fatal internal error.
Avoid interaction with udev. LVM will manage the relevant nodes in /dev
.I #DEFAULT_SYS_DIR#/lvm.conf
.I $HOME/.lvm_history
.BR lvm.conf (5),
.BR lvmcache (7),
.BR lvmthin (7),
.BR clvmd (8),
.BR dmsetup (8),
.BR lvchange (8),
.BR lvcreate (8),
.BR lvdisplay (8),
.BR lvextend (8),
.BR lvmchange (8),
.BR lvmconfig (8),
.BR lvmdiskscan (8),
.BR lvreduce (8),
.BR lvremove (8),
.BR lvrename (8),
.BR lvresize (8),
.BR lvs (8),
.BR lvscan (8),
.BR pvchange (8),
.BR pvck (8),
.BR pvcreate (8),
.BR pvdisplay (8),
.BR pvmove (8),
.BR pvremove (8),
.BR pvs (8),
.BR pvscan (8),
.BR vgcfgbackup (8),
.BR vgchange (8),
.BR vgck (8),
.BR vgconvert (8),
.BR vgcreate (8),
.BR vgdisplay (8),
.BR vgextend (8),
.BR vgimport (8),
.BR vgimportclone (8),
.BR vgmerge (8),
.BR vgmknodes (8),
.BR vgreduce (8),
.BR vgremove (8),
.BR vgrename (8),
.BR vgs (8),
.BR vgscan (8),
.BR vgsplit (8),
.BR readline (3)