vm uses qcow2 from unexisting storage

emoxam

Active Member
Apr 9, 2019
52
1
28
42
Thats a storages i got

Code:
pvesm status
Name           Type     Status           Total            Used       Available        %
NFS             nfs     active      1740348416      1443283968       208589824   82.93%
NFS2            nfs     active      1740348416      1617566720        34307072   92.94%
NFS3            nfs     active     18852987136      1443545728     17409441408    7.66%
backups        cifs     active     30165433924     10371538380     19793895544   34.38%
local           dir     active        25413876        10019948        14079932   39.43%

Code:
qm list
      VMID NAME                 STATUS     MEM(MB)    BOOTDISK(GB) PID
       109 CC-2--172.16.10.2    running    4096              64.00 15833

Code:
lsof -p 15833 | grep 109
kvm     15833 root    5wW     REG               0,24           6       847 /run/qemu-server/109.pid
kvm     15833 root   12u     unix 0x00000000b38276f3         0t0  13138451 /var/run/qemu-server/109.qmp type=STREAM
kvm     15833 root   18u      REG                8,4 68730224640   7077891 /opt/st2/images/109/vm-109-disk-0.qcow2
kvm     15833 root   25u     unix 0x00000000fa88a9de         0t0 933047703 /var/run/qemu-server/109.vnc type=STREAM

Code:
ls -l /opt/st2/images/109/
ls: cannot access '/opt/st2/images/109/': No such file or directory

Code:
 ls -l /opt/st2/images
total 36
drwxr-----  2 nobody nogroup 4096 Apr 16 12:52 108
drwxr-----  2 nobody nogroup 4096 Apr 16 12:29 111
drwxr-----  2 nobody nogroup 4096 Apr 16 12:30 113
drwxr-----  2 nobody nogroup 4096 Apr 16 12:30 114
drwxr-xr-x  2 nobody nogroup 4096 Feb 16  2021 dump
drwxr-xr-x 30 nobody nogroup 4096 Mar 31 13:35 images
drwxr-xr-x  2 nobody nogroup 4096 Feb 16  2021 private
drwxr-xr-x  2 nobody nogroup 4096 Feb 16  2021 snippets
drwxr-xr-x  4 nobody nogroup 4096 Feb 16  2021 template


Code:
 find / -name "*109*.qcow2"
find: ‘/mnt/pve/NFS2/lost+found’: Permission denied
find: ‘/mnt/pve/NFS-2/lost+found’: Permission denied
 
Maybe the storage existed before and has been delete? Because the qcow2 file was in use, it still exists and will only be remove when you stop the VM. I don't know of a way to reach that file when the directory where it was located is already gone. Maybe there is a way to recover files in limbo on Linux?
 
It's not that VM is so important, just wanted to know how it is possible!
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!