mirror of
git://sourceware.org/git/lvm2.git
synced 2025-10-26 07:33:16 +03:00
296fcd4c79
Drop misplaced letter 'I'.
Missing articles (a, an, the)
Incorrect prepositions (in/into, to/in)
Subject-verb agreement errors.
Awkward phrasing that needs smoothing.
Fixed prepositions ("prior to" instead of "prior the")
Corrected subject-verb agreement ("are becoming" instead of "is becoming")
Fixed word choices ("represents" instead of "presents")
Used consistent terminology ("environment" instead of "environmental")
Fixed pronoun references ("them" instead of "it" when referring to plural subjects)
Originated-by: warp-terminal
48 lines
2.2 KiB
Plaintext
48 lines
2.2 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, the VG can be extended with other PVs
|
|
(\fBvgextend\fP(8)), or existing LVs can be reduced or removed
|
|
(\fBlvremove\fP(8), \fBlvreduce\fP(8)).
|
|
.P
|
|
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.
|
|
.P
|
|
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.
|
|
.P
|
|
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.
|
|
.P
|
|
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 as references to the pools.
|
|
.P
|
|
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.
|
|
.P
|
|
VDO LVs are also provisioned volumes from a VDO pool, and are created with a
|
|
virtual size rather than a physical size (see \fBlvmvdo\fP(7)).
|
|
.
|
|
.SS Usage notes
|
|
.
|
|
In the usage section below, \fB--size\fP \fISize\fP can be replaced
|
|
with \fB--extents\fP \fINumber\fP. See descriptions in the options section.
|
|
.P
|
|
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.
|
|
.P
|
|
In the usage section below, when creating a pool and the name is omitted
|
|
the new LV pool name is generated with the
|
|
"vpool" prefix for vdo-pools and a unique numeric suffix.
|
|
.P
|
|
Pool name can be specified together with \fIVG\fP name i.e.:
|
|
vg00/mythinpool.
|