Hi, a 'quick' question. I've setup a modest sized ProxVE cluster, 3 nodes in an intel modular server with shared "SAS-SAN" storage between nodes for cluster:SAN VM storage pool / with LVM overlay (as per typical deployment recommendation).
I was curious, in this configuration, is there an 'easy' way to change (shrink) disk space allocation to a VM ? Since there is no 'direct' access to the underlying LVM 'filesystem' in this config .. typical under-the-hood method (qemu-img based ..) are not really accessible.
but - basically - there is no way to do this song and dance without doing a VM backup, restore, backup, restore cycle... ?
If I am missing something obvious, a friendly hint is greatly appreciated!
Thanks,
Tim
I was curious, in this configuration, is there an 'easy' way to change (shrink) disk space allocation to a VM ? Since there is no 'direct' access to the underlying LVM 'filesystem' in this config .. typical under-the-hood method (qemu-img based ..) are not really accessible.
Code:
I wonder thus, are my options: To Shrink the VM Disk allocation for example,
- Inside the VM, use Guest / OS-based tool to shrink the filesystem allocation (gparted or similar)
- Power off VM, backup, restore to different storage (NFS or local storage)
- reduce the size of the .RAW or QCOW (or whatever format it is..) VM image file on your filesystem-accessible location
- if required tweak config of the VM files to indicate size of file/virtual HDD (don't think this is actually required)
- take a backup of the VM again
- do a restore of the VM, and dump it back into the LVM storage/Shared SAN storage pool. OR dump onto another local:NFS:iSCSI shared SAN storage which you have available / which is appropriate / desired as resting place for the VM.If I am missing something obvious, a friendly hint is greatly appreciated!
Thanks,
Tim