Logical Volume Manager (LVM) – Proxmox VE

# pvs
  PV         VG   Fmt  Attr PSize PFree
  /dev/sda3  pve  lvm2 a--  7.87g 876.00m

# vgs
  VG   #PV #LV #SN Attr   VSize VFree
  pve    1   3   0 wz--n- 7.87g 876.00m

# lvs
  LV   VG   Attr       LSize   Pool Origin Data%  Meta%
  data pve  twi-a-tz--   4.38g             0.00   0.63
  root pve  -wi-ao----   1.75g
  swap pve  -wi-ao---- 896.00m

Summarize this content to 100 words

Most people install Proxmox VE directly on a local disk. The Proxmox VE
installation CD offers several options for local disk management, and
the current default setup uses LVM. The installer lets you select a
single disk for such setup, and uses that disk as physical volume for
the Volume Group (VG) pve. The following output is from a
test installation using a small 8GB disk:

# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 pve lvm2 a– 7.87g 876.00m

# vgs
VG #PV #LV #SN Attr VSize VFree
pve 1 3 0 wz–n- 7.87g 876.00m

The installer allocates three Logical Volumes (LV) inside this
VG:

# lvs
LV VG Attr LSize Pool Origin Data% Meta%
data pve twi-a-tz– 4.38g 0.00 0.63
root pve -wi-ao—- 1.75g
swap pve -wi-ao—- 896.00m

root

Formatted as ext4, and contains the operating system.

swap

Swap partition

data

This volume uses LVM-thin, and is used to store VM
images. LVM-thin is preferable for this task, because it offers
efficient support for snapshots and clones.

For Proxmox VE versions up to 4.1, the installer creates a standard logical
volume called “data”, which is mounted at /var/lib/vz.

Starting from version 4.2, the logical volume “data” is a LVM-thin pool,
used to store block based guest images, and /var/lib/vz is simply a
directory on the root file system.

Source link