]> git.proxmox.com Git - pve-docs.git/blame - pve-storage-lvm.adoc
pvecm: fix wrong quorum numbers
[pve-docs.git] / pve-storage-lvm.adoc
CommitLineData
8119f671 1[[storage_lvm]]
aa039b0f
DM
2LVM Backend
3-----------
5f09af76
DM
4ifdef::wiki[]
5:pve-toplevel:
cb84ed18 6:title: Storage: LVM
5f09af76
DM
7endif::wiki[]
8
aa039b0f
DM
9Storage pool type: `lvm`
10
7de448c2 11LVM is a light software layer on top of hard disks and partitions. It
aa039b0f
DM
12can be used to split available disk space into smaller logical
13volumes. LVM is widely used on Linux and makes managing hard drives
14easier.
15
16Another use case is to put LVM on top of a big iSCSI LUN. That way you
17can easily manage space on that iSCSI LUN, which would not be possible
18otherwise, because the iSCSI specification does not define a
19management interface for space allocation.
20
5eba0743 21
aa039b0f
DM
22Configuration
23~~~~~~~~~~~~~
24
25The LVM backend supports the common storage properties `content`, `nodes`,
26`disable`, and the following LVM specific properties:
27
28`vgname`::
29
30LVM volume group name. This must point to an existing volume group.
31
32`base`::
33
34Base volume. This volume is automatically activated before accessing
35the storage. This is mostly useful when the LVM volume group resides
36on a remote iSCSI server.
37
38`saferemove`::
39
40Zero-out data when removing LVs. When removing a volume, this makes
41sure that all data gets erased.
42
43`saferemove_throughput`::
44
8c1189b6 45Wipe throughput (`cstream -t` parameter value).
aa039b0f 46
8c1189b6 47.Configuration Example (`/etc/pve/storage.cfg`)
aa039b0f
DM
48----
49lvm: myspace
50 vgname myspace
51 content rootdir,images
52----
53
54File naming conventions
55~~~~~~~~~~~~~~~~~~~~~~~
56
57The backend use basically the same naming conventions as the ZFS pool
58backend.
59
60 vm-<VMID>-<NAME> // normal VM images
61
62Storage Features
63~~~~~~~~~~~~~~~~
64
65LVM is a typical block storage, but this backend does not support
66snapshot and clones. Unfortunately, normal LVM snapshots are quite
67inefficient, because they interfere all writes on the whole volume
68group during snapshot time.
69
70One big advantage is that you can use it on top of a shared storage,
71for example an iSCSI LUN. The backend itself implement proper cluster
72wide locking.
73
74TIP: The newer LVM-thin backend allows snapshot and clones, but does
75not support shared storage.
76
77
78.Storage features for backend `lvm`
79[width="100%",cols="m,m,3*d",options="header"]
80|==============================================================================
81|Content types |Image formats |Shared |Snapshots |Clones
82|images rootdir |raw |possible |no |no
83|==============================================================================
84
85Examples
86~~~~~~~~
87
88List available volume groups:
89
90 # pvesm lvmscan
91
deb4673f
DM
92ifdef::wiki[]
93
94See Also
95~~~~~~~~
96
f532afb7 97* link:/wiki/Storage[Storage]
deb4673f
DM
98
99endif::wiki[]
aa039b0f
DM
100
101