mirror of
git://sourceware.org/git/lvm2.git
synced 2025-01-18 10:04:20 +03:00
29 lines
1.4 KiB
Plaintext
29 lines
1.4 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.
|
|
|