Understanding the PVE/LV/PV/VG

[aRustyDev]

I have been trying to make sense of what these terms actually mean, and how they relate to each other.
I just got my Proxmox VE up and running and started loading in ISO's when I started getting "no space available" messages (ridiculous, I have 10 TB...)
So now I'm trying to understand what I need to do to resize my disks correctly, but I can't seem to make sense of the terms.

Do these terms stack like nesting dolls?
I'm understanding that I need a non-thin LVM (I think) to store my ISO's on, and I think it needs to be a directory?

I think I'd like to try and partition/logically separate a few major items.
1. ISO's
2. Backups & Snapshots
3. Proxmox OS files
4. Containers & Image files

Is this a reasonable way to split out my files? If not, can you explain why? If it is reasonable, can you give an example of what that might look like?

Any explanations would be very much appreciated, I'm definitely missing something that must be considered implicit in the documentation

Here's a snip of output, I decided to just go ahead and clean the root drive for now, and re-copy the ISO's when I've fixed the volume issue.

 

[aRustyDev]

I seem to have found a solution to this, though I am still not sure what I was doing wrong, or why it was wrong.
So any comments are still welcome!

# remove pve-data logical volume.
lvremove /dev/pve/data -y

# create it again with new size.
lvcreate -L 10G -n data pve -T

# give pve-root all the other size.
lvresize -l +100%FREE /dev/pve/root

# resize pve-root file system
resize2fs /dev/mapper/pve-root

Source

 

[fabian]

the terminology works like this:

• PV (physical volume) is a block device or parts of it, it's where the data is actually stored
• VG (volume group) a grouping of one or more PVs
• LV (logical volume) a volume stored on a VG
• thin pool - a special set of volumes that can store regular LVs without allocating the full size from the start

the default setup with PVE and LVM is to have one PV (disk), with one VG ('pve'), with one volume each for 'root' (mounted on '/'), 'swap' (used as swap) and 'data' (a thin pool getting most of the space, used for guest volumes). a directory storage for backups, iso files, templates is also defined on top of the root file system/LV, but it does not have much space.

if you need more space to store backups/.. on your LVM storage, I would allocate a regular LV on the 'data' pool, mount that somewhere and define a 'dir' type storage for that mountpoint. removing the 'data' thinpool means you lose the LVM thin features like snapshots, overprovisioning for both VMs and CTs.

https://pve.proxmox.com/pve-docs/pve-admin-guide.html#chapter_lvm might be of interest as well