]> git.proxmox.com Git - pve-docs.git/blob - local-lvm.adoc
use ADOC_STDARG to compile pve-admin-guide.html
[pve-docs.git] / local-lvm.adoc
1 Logical Volume Manager (LVM)
2 ----------------------------
3 include::attributes.txt[]
4 ifdef::wiki[]
5 :pve-toplevel:
6 endif::wiki[]
7
8 Most people install {pve} directly on a local disk. The {pve}
9 installation CD offers several options for local disk management, and
10 the current default setup uses LVM. The installer let you select a
11 single disk for such setup, and uses that disk as physical volume for
12 the **V**olume **G**roup (VG) `pve`. The following output is from a
13 test installation using a small 8GB disk:
14
15 ----
16 # pvs
17 PV VG Fmt Attr PSize PFree
18 /dev/sda3 pve lvm2 a-- 7.87g 876.00m
19
20 # vgs
21 VG #PV #LV #SN Attr VSize VFree
22 pve 1 3 0 wz--n- 7.87g 876.00m
23 ----
24
25 The installer allocates three **L**ogical **V**olumes (LV) inside this
26 VG:
27
28 ----
29 # lvs
30 LV VG Attr LSize Pool Origin Data% Meta%
31 data pve twi-a-tz-- 4.38g 0.00 0.63
32 root pve -wi-ao---- 1.75g
33 swap pve -wi-ao---- 896.00m
34 ----
35
36 root:: Formatted as `ext4`, and contains the operation system.
37
38 swap:: Swap partition
39
40 data:: This volume uses LVM-thin, and is used to store VM
41 images. LVM-thin is preferable for this task, because it offers
42 efficient support for snapshots and clones.
43
44 Hardware
45 ~~~~~~~~
46
47 We highly recommend to use a hardware RAID controller (with BBU) for
48 such setups. This increases performance, provides redundancy, and make
49 disk replacements easier (hot-pluggable).
50
51 LVM itself does not need any special hardware, and memory requirements
52 are very low.
53
54
55 Bootloader
56 ~~~~~~~~~~
57
58 We install two boot loaders by default. The first partition contains
59 the standard GRUB boot loader. The second partition is an **E**FI **S**ystem
60 **P**artition (ESP), which makes it possible to boot on EFI systems.