Single disk, best practice, delete local-lvm and resize?

[jaxjexjox]

I only have a 256GB NVMe disk which proxmox will barely use 15% of ever.
According to this youtube video:
https://youtu.be/1q4_suDXr4M?t=728
He's suggesting I remove the local-lvm partition and then re-size as follows in the shell.

#1. lvremove /dev/pve/data
#2. lvresize -l +100%FREE /dev/pve/root
#3. resize2fs /dev/mapper/pve-root

Then change content flags on the primary drive to enable VZDump, Disk Image, ISO image, Container template etc (the whole lot basically)


Something about this feels wrong to me but I thought I'd defer to the pros, what is the best way to do this on a small, simple homelab?

 

[dylanw]

There's nothing entirely wrong with doing this, but it depends on what you prefer. The difference will be that on the lvm-thin volume ('data') offers block-level storage with thin-provisioning and snapshots, so the slightly higher performance 'raw' drive type can be used and each VM will get its own volume. On the directory storage ('local'), VMs are stored as single files, meaning that a lower-performing format such as Qcow2 must be used if you would like thin-provisioning and snapshots.
For a homelab/non-enterprise setup, especially with an NVMe drive, I don't think you'll have issues with either choice

 

[jaxjexjox]

Hey thanks for the reply.

I read a little more online and it seems to me, that there's no problem installing proxmox across the entire primary drive, it'll still work fine.
I do like thin provisioning if I recall what it is. (I run some on TrueNAS core and I love my ZSTD high compression drive, where the sparse VMs chew very little real disk space)
(and yes, I know, never fill the disk!)

Is that the same thing, right?

 

[aschneder]

Hello guys! I just did that and now I'm aware about the snapshot limitation... Is it possible to revert this, without havint to reinstall the entire machine? Thanks.