Disk image storage low on disk space + Restore

[fnatter]

Dear Proxmox experts,

my storage pool has a single raw disk image (790G) and "lvs"
reports only 3GB free in the pool:

root@sidact104:~# lvs -a pve
  LV              VG  Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  data            pve twi-aotz-- <793.80g             87.68  3.33                           
  [data_tdata]    pve Twi-ao---- <793.80g                                                   
  [data_tmeta]    pve ewi-ao----   <8.10g                                                   
  [lvol0_pmspare] pve ewi-------   <8.10g                                                   
  root            pve -wi-ao----   96.00g                                                   
  swap            pve -wi-ao----    8.00g                                                   
  vm-100-disk-0   pve Vwi-aotz--  790.00g data        88.10

For later: Can I do an in-place-restore (same vmid) in this configuration,
or are temp files / metadata files kicking in (metadata is already deducted?)?

Also, do I need to watch out for something in vm -> Backup -> Restore dialog?

Many Thanks and Best Regards,
Felix

 

[kawano-y]

Hi,

The Data% value of 87.68% indicates that approximately 12% of the LVM-thin pool's physical space is still available.

The 3 GB of free space you mentioned may refer to unallocated space in the volume group rather than free space within the thin pool.

However, restoring to the same VMID does not necessarily mean that the existing disk space will be reused in place, so sufficient free space is still required.

 

[fnatter]

hello,
how about this?

* free space on another 1tb storage
* restore (with different vmid) to that storage
* start, test new vm
* delete original vm (do not prune job configs?)
* disk -> Move storage, to original storage

Many Thanks and Best Regards,
Felix

 

[kawano-y]

Hi,

Yes, that sounds like a reasonable approach.

Restoring to another storage with a different VMID would allow you to test the restored VM before deleting the original one.

Just keep in mind that moving the disk back to the original storage will not change the new VMID. You should also check any backup or replication jobs that reference the original VMID.