Noob question about OVF import and PVE disk allocations (/var/tmp/) and such

[mbarnickle]

I am relatively new to Proxmox though I've worked with VMWare for decades. Before I go all in on Proxmox I'm doing some hands on testing in my home lab. I have a Beelink GTR9-Pro with 128GB RAM and a 2TB NVMe drive for storage. It should be enough for me to learn the lay of the land.

I've installed Proxmox, deployed a few containers, and successfully converted one vanilla Windows VM from VMware (stand alone, not messing with ESXi yet) to a working VM. Good enough, slowly learning as I go. But I've hit a problem around storage that I cannot figure out.

The Windows VM I converted was small, with a 10Gb HDD. I won't drag you through those details because they are only relevant to say "OVF import worked and that VM works." When I try to import a larger working VM things go awry. I've already used OVF tool to convert the image. This resulted in two vmdk files of roughly 60GB and 250GB. When I try to import the 60GB vmdk using the proxmox GUI I get the following error:

starting file import from: /var/tmp/pveupload-af39f071e5ef790606b290a45b9d32a4
target node: pve
target file: /var/lib/vz/import/ForgeVM-disk1.vmdk
file size is: 59147923456
command: cp -- /var/tmp/pveupload-af39f071e5ef790606b290a45b9d32a4 /var/lib/vz/import/ForgeVM-disk1.vmdk
TASK ERROR: import failed: cp: error copying '/var/tmp/pveupload-af39f071e5ef790606b290a45b9d32a4' to '/var/lib/vz/import/ForgeVM-disk1.vmdk': No space left on device

Before we even get into my request for you folks to lay some knowledge on me, help me understand the details I should post. You know, so you can point out "I see the issue, your head doesn't actually belong in that orifice!" and such.

Seeing my issue above, what Proxmox commands generate the correct details for you to even know what my issue is (other than ignorance)?

 

[woma]

Maybe you did that already ...

Check available space of /var/lib/vz with df -h
As my test system has only 28GB available space a 60GB import task would fail, too.

oot@node3:~# df -h
Filesystem        Size  Used Avail Use% Mounted on
...
rpool/var-lib-vz   28G  101M   28G   1% /var/lib/vz
...

My storage is too small, so I would have to allow "import" content (datacenter>storage and Edit button) for another storage that is big enough and use that for import of that 60GB VM.

If your storage is big enough but has no free space, I would check directories with find /var/lib/vz -type d -exec du -sh {} \;
Backups, ISO files, VM disks etc. could be stored there and use up space.
Maybe prior failed imports did not clean up their files. If so I would expect big amount of data in "import" directory.

Output looks like that and gives occupied space per directory, in my case everything is "empty" after fresh install.

root@node3:~# find /var/lib/vz -type d -exec du -sh {} \;
3.5K    /var/lib/vz
512     /var/lib/vz/images
512     /var/lib/vz/import
512     /var/lib/vz/dump
1.5K    /var/lib/vz/template
512     /var/lib/vz/template/cache
512     /var/lib/vz/template/iso