[SOLVED] Move disk image from full storage

Jul 28, 2020
14
0
6
44
Folks,

New to Proxmox, so bear with me.

I created a Linux (Ubuntu) VM with a 500GB partition for the OS and a 3.5TB partition for storage. Anyway, I accidentally created the image file for the 500GB OS partition in the default "iso" container. Everything worked well until the image file filled up the 99GB of storage and the VM OS crashed. I tried to move it, but Proxmox complained that no space was available. I had the "great" idea to detach the hard drive image from the VM and now I don't know what to do. The image file is still there, but I am not sure the best way to move it. Can someone help? I am somewhat comfortable with Linux, but I am pretty new to Proxmox.
 
Last edited:
What kind of storage is the one that you would like the disk to be moved to?

Can you show the contents of /etc/pve/storage.vfg and the config of the VM? [qm config <vmid>[/icode]
 
dir: local
path /var/lib/vz
content vztmpl,iso,backup

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

dir: iso
path /root
content images
shared 0
 
I think I got it. I simply deleted some ISOs that were in dir: local which seemed to free up just enough space in dir: iso for me to move the virtual HD to lvmthin. I don't really understand how lvmthin works (it does not seem to be mounted to the Linux file system) but as long as it's some sort of space I can put my VM disks, I'll take it.
 
The LVM is a logical volume manager. For VM disks we create a logical volume and use that directly as block device for the VM. No files or directories there.

The solution you found is the one that I would have suggested now, after confirming to which kind of storage you want to move the disk. In order to move it, it needs to be cached somewhere and for that a bit of space is needed.

Thanks for posting the resolution of the problem. Would you please be so kind to mark the thread as solved? To do so, edit the first post and select the prefix in the dropdown next to the title. :)
 
Interesting. I don't know the Logical Volume Manager very well and have only seen it being used to create volumes which are mounted to the Linux file system. I didn't realize that a hypervisor could use it directly for block devices like that. Cool stuff :)