Why do my VM files take 10x the size they should?

[devawpz]

I have a VM on a node, and I see in storage that it takes up to 10x the size (maybe more).
These are the files for a 65GB VM:

root@host:/# cd /mnt/store/images/110

root@host:/mnt/store/images/110# ls -l
total 147052708
-rw-r--r-- 1 root root 68730355712 Oct 20 12:54 vm-110-disk-0.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:52 vm-110-disk-10.qcow2
-rw-r----- 1 root root 68730355712 Oct 20 15:31 vm-110-disk-11.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:24 vm-110-disk-1.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:15 vm-110-disk-2.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:03 vm-110-disk-3.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:34 vm-110-disk-4.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:44 vm-110-disk-5.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:13 vm-110-disk-6.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:23 vm-110-disk-7.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:33 vm-110-disk-8.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:43 vm-110-disk-9.qcow2

This happens to several of the VMs.
If I migrate them to another node, this still keeps happening.
What could be wrong?
Is there any way I can get the space back?

Would appreciate any help with this.

 

[devawpz]

In the GUI, the file that is connected to the HD is only the last one, vm-110-disk-11.qcow2.

Can I safely delete the other files, or will I regret it?

 

[fabian]

that's a question only you can answer

 

[oguz]

I have a VM on a node, and I see in storage that it takes up to 10x the size (maybe more).
These are the files for a 65GB VM:

root@host:/# cd /mnt/store/images/110

root@host:/mnt/store/images/110# ls -l
total 147052708
-rw-r--r-- 1 root root 68730355712 Oct 20 12:54 vm-110-disk-0.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:52 vm-110-disk-10.qcow2
-rw-r----- 1 root root 68730355712 Oct 20 15:31 vm-110-disk-11.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:24 vm-110-disk-1.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:15 vm-110-disk-2.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:03 vm-110-disk-3.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:34 vm-110-disk-4.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 12:44 vm-110-disk-5.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:13 vm-110-disk-6.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:23 vm-110-disk-7.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:33 vm-110-disk-8.qcow2
-rw-r--r-- 1 root root 68730355712 Oct 20 13:43 vm-110-disk-9.qcow2

This happens to several of the VMs.
If I migrate them to another node, this still keeps happening.
What could be wrong?
Is there any way I can get the space back?

Would appreciate any help with this.

each file is around 65G but there are multiple of them? they're all the same size so if i had to guess these could be leftover from cloning the disks or editing the config manually.

In the GUI, the file that is connected to the HD is only the last one, vm-110-disk-11.qcow2.

Can I safely delete the other files, or will I regret it?

run qm rescan and it should rescan your disks for the volumes and add them accordingly to the configuration as "unused" disks.

afterwards you can mount them on your VM and check if you need anything and decide if you should delete them.

hope this helps

 

[devawpz]

Thanks, I ended up moving them to another place and deleting them. Didn't recognized them as anything else than possible versions of a migration, so in the end that's what I did.