mirror of
git://sourceware.org/git/lvm2.git
synced 2024-10-28 03:27:58 +03:00
36cac41115
Commitsa29bb6a14b...5c199d99f4narrowed down on addressing the escaping of hyphens in the dynamic creation of manuals whilst avoiding them in creating help texts. This lead to a sequence of slipping through hyphens adrressed by additional patches in aforementioned commit series. On the other hand, postprocessing dynamically man-generator created and statically provided manuals catches all hyphens in need of escaping. Changes: - revert the above commits whilst keeping man-generator streamlining and the detection of any '\' when generating help texts in order to avoid escapes to slip in - Dynamically escape hyphens in manaual pages using sed(1) in the respective Makefile targets - remove any manually added escaping on hyphens from any static manual sources or headers
37 lines
1.8 KiB
Plaintext
37 lines
1.8 KiB
Plaintext
lvcreate creates a new LV in a VG. For standard LVs, this requires
|
|
allocating logical extents from the VG's free physical extents. If there
|
|
is not enough free space, then the VG can be extended (see
|
|
\fBvgextend\fP(8)) with other PVs, or existing LVs can be reduced or
|
|
removed (see \fBlvremove\fP, \fBlvreduce\fP.)
|
|
|
|
To control which PVs a new LV will use, specify one or more PVs as
|
|
position args at the end of the command line. lvcreate will allocate
|
|
physical extents only from the specified PVs.
|
|
|
|
lvcreate can also create snapshots of existing LVs, e.g. for backup
|
|
purposes. The data in a new snapshot LV represents the content of the
|
|
original LV from the time the snapshot was created.
|
|
|
|
RAID LVs can be created by specifying an LV type when creating the LV (see
|
|
\fBlvmraid\fP(7)). Different RAID levels require different numbers of
|
|
unique PVs be available in the VG for allocation.
|
|
|
|
Thin pools (for thin provisioning) and cache pools (for caching) are
|
|
represented by special LVs with types thin-pool and cache-pool (see
|
|
\fBlvmthin\fP(7) and \fBlvmcache\fP(7)). The pool LVs are not usable as
|
|
standard block devices, but the LV names act references to the pools.
|
|
|
|
Thin LVs are thinly provisioned from a thin pool, and are created with a
|
|
virtual size rather than a physical size. A cache LV is the combination of
|
|
a standard LV with a cache pool, used to cache active portions of the LV
|
|
to improve performance.
|
|
.SS Usage notes
|
|
In the usage section below, \fB--size\fP \fISize\fP can be replaced
|
|
with \fB--extents\fP \fINumber\fP. See both descriptions
|
|
the options section.
|
|
|
|
In the usage section below, \fB--name\fP is omitted from the required
|
|
options, even though it is typically used. When the name is not
|
|
specified, a new LV name is generated with the "lvol" prefix and a unique
|
|
numeric suffix. Also see the description in the options section.
|