root@host:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert data pve -wi-ao---- 321.75g root pve -wi-ao---- 96.00g swap pve -wi-ao---- 31.00g
The output of the lvs command shows that you have five logical volumes allocated from the physical volume group "pve". The root and swap volumes are regular volumes that are used for your root filesystem and swap.So, my friend kind of explained it to me, and showed me the math using the lvs command.
Here is mine: View attachment 9902
So, I do have 5 volume, even though I thought I only had 2. He said he doesn't know how EXACTLY the math works, but that data is basically a 'close sum' of the vm disks I have.
That's indeed true in my case.
OK - so I don't need to be worried about running out?The whole size of the volume is considered allocated as far as the volume manager is concerned and you can't over-commit.
Um, maybe. I mis-spoke a bit. If you are using qcow2 format VM disks, they behave similar to lvm-thin in that space isn't acquired until it is used. In that case you can declare a VM disk or group that total a size that is bigger than the actual storage.That's indeed true in my case.
OK - so I don't need to be worried about running out?
Filesystem Size Used Avail Use% Mounted on udev 16G 0 16G 0% /dev tmpfs 3.2G 306M 2.9G 10% /run /dev/mapper/pve-root 95G 6.3G 84G 7% / tmpfs 16G 37M 16G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 16G 0 16G 0% /sys/fs/cgroup /dev/sda2 486M 191M 271M 42% /boot /dev/mapper/pve-data 317G 160G 157G 51% /var/lib/vz /dev/fuse 30M 36K 30M 1% /etc/pve tmpfs 3.2G 0 3.2G 0% /run/user/1000
root@host:~$ pvs PV VG Fmt Attr PSize PFree /dev/sda3 pve lvm2 a-- 464.75g 16.00g