local-lvm.adoc

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