инструменты LVM2 (LVM2 tools)
VALID NAMES
The valid characters for VG and LV names are: a-z A-Z 0-9 + _ . -
VG names cannot begin with a hyphen. The name of a new LV also
cannot begin with a hyphen. However, if the configuration
setting metadata/record_lvs_history is enabled then an LV name
with a hyphen as a prefix indicates that, although the LV was
removed, it is still being tracked because it forms part of the
history of at least one LV that is still present. This helps to
record the ancestry of thin snapshots even after some links in
the chain have been removed. A reference to the historical LV
'lvol1' in VG 'vg00' would be 'vg00/-lvol1' or just '-lvol1' if
the VG is already set. (The latter form must be preceded by '--'
to terminate command line option processing before reaching this
argument.)
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', '_iorig',
'_mimage', '_mlog', '_pmspare', '_rimage', '_rmeta', '_tdata',
'_tmeta', '_vdata', '_vorigin' or '_wcorig'. 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 dmsetup splitname to separate out the
original VG, LV and internal layer names.
