TASK ERROR: rbd error: rbd: listing images failed

powersupport

Active Member
Jan 18, 2020
249
2
38
29
Hi,

We recently faced an issue with the Proxmox when trying to delete the template or VM. please find the attached screenshot.

As per your suggestion in a previous thread, we have created in Proxmox storage a storage named "rbd-vm".But the issue still persists.

TASK ERROR: rbd error: rbd: listing images failed: (2) No such file or directory

Please have a look.

Regards,
 
hi,
We recently faced an issue with the Proxmox when trying to delete the template or VM. please find the attached screenshot.
there is no screeshot attached..

can you please post the vm config as well as the storage config and the command you try to execute?
 
Hi,

Please be informed that we have tried to delete Templates from the frontend not using the commands

Please refer to the files attached.

Thank you.


config satapx.PNGerror.PNG
errorlog.PNG
 
like i wrote, please post the vm config (qm config ID) and the storage config too (/etc/pve/storage.cfg)
 
HI,
qm config 106 the command showing " Configuration file 'nodes/pnode-sg1-n1/qemu-server/106.conf' does not exist"
Showing same for all VMs
Also,

cat /etc/pve/storage.cfg
dir: local
path /var/lib/vz
content iso
shared 0

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

rbd: satapx-storage
content images,rootdir
krbd 0
pool satapx-storage

nfs: NFS-ISO
export /mnt/iso
path /mnt/pve/NFS-ISO
server 103.3.164.251
content vztmpl,iso,backup
prune-backups keep-last=5

nfs: NFS-VM-backup
export /home/nfsproxmox
path /mnt/pve/NFS-VM-backup
server 117.120.4.114
content backup,images,vztmpl,rootdir,iso
prune-backups keep-last=5
 
Last edited:
qm config 106 the command showing " Configuration file 'nodes/pnode-sg1-n1/qemu-server/106.conf' does not exist"
Showing same for all VMs
is it a container? in that case use 'pct config ID'
 
ok then you must run the 'qm config' command on the node where the vm is....
 
Hi,

Here is the qm config output.


agent: 1
boot: order=scsi0;ide2;net0
cores: 6
ide2: NFS-ISO:iso/CentOS-7-x86_64-Minimal-1810__2_.iso,media=cdrom
memory: 63488
name: test-bu-server
net0: virtio=12:04:6C:EA:9F:47,bridge=vmbr0,firewall=1
numa: 0
ostype: l26
scsi0: satapx-storage:vm-127-disk-0,size=500G
scsihw: virtio-scsi-pci
smbios1: uuid=8f4cd2d6-212a-4165-a244-66b473d23bdc
sockets: 2
vmgenid: b430c56b-bda8-4bda-8af5-a5a01b4abc46

Regards,
 
ok so what is the output of 'pvesm status' and 'pvesm list satapx-storage' ?
 
Hi,

Please find the outputs of 'pvesm status' and 'pvesm list satapx-storage'.

root@pxvm:~# pvesm status
Name Type Status Total Used Available %
NFS-ISO nfs active 524276736 232446208 291830528 44.34%
local dir active 98559220 9820244 83689428 9.96%
local-lvm lvmthin active 335646720 0 335646720 0.00%
satapx-storage rbd active 47677968555 15707891883 31970076672 32.95%

root@pxvm:~# pvesm list satapx-storage
rbd error: rbd: listing images failed: (2) No such file or directory
 
ok it seems the rbd command fails for some reason...

can youpost the ouput of the following two commands?
Code:
rbd -p satapx-storage list
rbd -p satapx-storage list --long
 
Hi,

Please find the below results.

root@pxvm:~# rbd -p satapx-storage list
base-106-disk-0
base-107-disk-0
base-110-disk-0
base-111-disk-0
base-112-disk-0
base-113-disk-0
base-114-disk-0
base-115-disk-0
base-120-disk-0
base-125-disk-0
base-126-disk-0
base-134-disk-0
base-135-disk-0
base-136-disk-0
base-137-disk-0
base-139-disk-0
base-144-disk-0
base-147-disk-0
vm-100-cloudinit
vm-100-disk-0
vm-1004-cloudinit
vm-1004-disk-0
vm-101-cloudinit
vm-101-disk-0
vm-101-disk-1
vm-101-disk-2
vm-102-cloudinit
vm-102-disk-0
vm-103-cloudinit
vm-103-disk-0
vm-104-cloudinit
vm-104-disk-0
vm-104-disk-1
vm-105-cloudinit
vm-105-disk-0
vm-106-cloudinit
vm-107-cloudinit
vm-108-cloudinit
vm-108-disk-0
vm-109-cloudinit
vm-109-disk-0
vm-110-cloudinit
vm-111-cloudinit
vm-112-cloudinit
vm-113-cloudinit
vm-114-cloudinit
vm-115-cloudinit
vm-116-cloudinit
vm-116-disk-0
vm-117-cloudinit
vm-117-disk-0
vm-118-cloudinit
vm-118-disk-0
vm-119-cloudinit
vm-120-cloudinit
vm-121-cloudinit
vm-121-disk-0
vm-123-cloudinit
vm-123-disk-0
vm-124-cloudinit
vm-124-disk-0
vm-125-cloudinit
vm-126-cloudinit
vm-128-cloudinit
vm-128-disk-0
vm-134-cloudinit
vm-135-cloudinit
vm-136-cloudinit
vm-137-cloudinit
vm-139-cloudinit
vm-144-cloudinit
vm-121-cloudinit
root@pxvm:~# rbd -p satapx-storage list --long
rbd: error opening vm-121-cloudinit: (2) No such file or directory
rbd: error opening vm-121-cloudinit: (2) No such file or directory
NAME SIZE PARENT FMT PROT LOCK
base-106-disk-0 30 GiB 2
base-106-disk-0@__base__ 30 GiB 2 yes
base-107-disk-0 20 GiB 2
base-107-disk-0@__base__ 20 GiB 2 yes
base-110-disk-0 50 GiB 2
base-110-disk-0@__base__ 50 GiB 2 yes
base-111-disk-0 50 GiB 2
base-111-disk-0@__base__ 50 GiB 2 yes
base-112-disk-0 30 GiB 2
base-112-disk-0@__base__ 30 GiB 2 yes
base-113-disk-0 10 GiB 2
base-113-disk-0@__base__ 10 GiB 2 yes
base-114-disk-0 50 GiB 2
base-114-disk-0@__base__ 50 GiB 2 yes
base-115-disk-0 30 GiB 2
base-115-disk-0@__base__ 30 GiB 2 yes
base-120-disk-0 50 GiB 2
base-120-disk-0@__base__ 50 GiB 2 yes
base-125-disk-0 20 GiB 2
base-125-disk-0@__base__ 20 GiB 2 yes
base-126-disk-0 80 GiB 2
base-126-disk-0@__base__ 80 GiB 2 yes
base-134-disk-0 50 GiB 2
base-134-disk-0@__base__ 50 GiB 2 yes
base-135-disk-0 30 GiB 2
base-135-disk-0@__base__ 30 GiB 2 yes
base-136-disk-0 30 GiB 2
base-136-disk-0@__base__ 30 GiB 2 yes
base-137-disk-0 20 GiB 2
base-137-disk-0@__base__ 20 GiB 2 yes
base-139-disk-0 50 GiB 2
base-139-disk-0@__base__ 50 GiB 2 yes
base-144-disk-0 20 GiB 2
base-144-disk-0@__base__ 20 GiB 2 yes
base-147-disk-0 30 GiB 2
base-147-disk-0@__base__ 30 GiB 2 yes
vm-100-cloudinit 4 MiB 2
vm-100-disk-0 20 GiB 2
vm-1004-cloudinit 4 MiB 2
vm-1004-disk-0 10 TiB 2 excl
vm-101-cloudinit 4 MiB 2
vm-101-disk-0 50 GiB 2 excl
vm-101-disk-1 32 GiB 2 excl
vm-101-disk-2 2 TiB 2 excl
vm-102-cloudinit 4 MiB 2
vm-102-disk-0 5 TiB 2 excl
vm-103-cloudinit 4 MiB 2
vm-103-disk-0 10 GiB 2 excl
vm-104-cloudinit 4 MiB 2
vm-104-disk-0 6.3 TiB 2 excl
vm-104-disk-1 1 MiB 2
vm-105-cloudinit 4 MiB 2
vm-105-disk-0 50 GiB 2
vm-106-cloudinit 4 MiB 2
vm-107-cloudinit 4 MiB 2
vm-108-cloudinit 4 MiB 2
vm-108-disk-0 10 GiB 2 excl
vm-109-cloudinit 4 MiB 2
vm-109-disk-0 50 GiB 2
vm-110-cloudinit 4 MiB 2
vm-111-cloudinit 4 MiB 2
vm-112-cloudinit 4 MiB 2
vm-113-cloudinit 4 MiB 2
vm-114-cloudinit 4 MiB 2
vm-115-cloudinit 4 MiB 2
vm-116-cloudinit 4 MiB 2
vm-116-disk-0 50 GiB 2
vm-117-cloudinit 4 MiB 2
vm-117-disk-0 50 GiB 2
vm-118-cloudinit 4 MiB 2
vm-118-disk-0 180 GiB 2
vm-119-cloudinit 4 MiB 2
vm-120-cloudinit 4 MiB 2
vm-121-disk-0 6.3 TiB 2
vm-123-cloudinit 4 MiB 2
vm-123-disk-0 20 GiB 2 excl
vm-124-cloudinit 4 MiB 2
vm-124-disk-0 10 GiB 2 excl
vm-125-cloudinit 4 MiB 2
vm-126-cloudinit 4 MiB 2
vm-128-cloudinit 4 MiB 2
vm-128-disk-0 2 TiB 2 excl
vm-134-cloudinit 4 MiB 2
vm-135-cloudinit 4 MiB 2
vm-136-cloudinit 4 MiB 2
vm-137-cloudinit 4 MiB 2
vm-139-cloudinit 4 MiB 2
vm-144-cloudinit 4 MiB 2
rbd: listing images failed: (2) No such file or directory
root@pxvm:~#
 
rbd: error opening vm-121-cloudinit: (2) No such file or directory
rbd: error opening vm-121-cloudinit: (2) No such file or directory
ok it seems there is something wrong with that image.
since it's only the cloud init image (which will be autogenerated anyway) could you try to delete that with
Code:
rbd -p satapx-storage rm vm-121-cloudinit

EDIT: make sure the vm is not online at that moment!
 
Hi,

Please note that we are facing the rbd error issue for all the VM's.

May I know the "VM-121-cloud-init" issue causes the entire rbd issue?

Also, in this case, can I confirm "vm-126-cloudinit" have no issues.

Regards.
 
i cannot guarantee anything, but it seems to me like ceph is somehow confused about this particular image and throws an error with the '--long' parameter which leads to the error message in the original post
by removing that image, i'd hope to clear that error and you can continue with the original task...
 
Hi,

I have removed the image-121 but it shows the same error when we are trying to remove another VM.

root@pxvm:~# rbd -p satapx-storage list
base-106-disk-0
base-107-disk-0
base-110-disk-0
base-111-disk-0
base-112-disk-0
base-113-disk-0
base-114-disk-0
base-115-disk-0
base-120-disk-0
base-125-disk-0
base-126-disk-0
base-134-disk-0
base-135-disk-0
base-136-disk-0
base-137-disk-0
base-139-disk-0
base-144-disk-0
base-147-disk-0
vm-100-cloudinit
vm-100-disk-0
vm-1004-cloudinit
vm-1004-disk-0
vm-101-cloudinit
vm-101-disk-0
vm-101-disk-1
vm-101-disk-2
vm-102-cloudinit
vm-102-disk-0
vm-103-cloudinit
vm-103-disk-0
vm-104-cloudinit
vm-104-disk-0
vm-104-disk-1
vm-105-cloudinit
vm-105-disk-0
vm-106-cloudinit
vm-107-cloudinit
vm-108-cloudinit
vm-108-disk-0
vm-109-cloudinit
vm-109-disk-0
vm-110-cloudinit
vm-111-cloudinit
vm-112-cloudinit
vm-113-cloudinit
vm-114-cloudinit
vm-115-cloudinit
vm-116-cloudinit
vm-116-disk-0
vm-117-cloudinit
vm-117-disk-0
vm-118-cloudinit
vm-118-disk-0
vm-119-cloudinit
vm-120-cloudinit
vm-121-cloudinit
vm-121-disk-0
vm-123-cloudinit
vm-123-disk-0
vm-124-cloudinit
vm-124-disk-0
vm-125-cloudinit
vm-126-cloudinit
vm-128-cloudinit
vm-128-disk-0
vm-134-cloudinit
vm-135-cloudinit
vm-136-cloudinit
vm-137-cloudinit
vm-139-cloudinit
vm-144-cloudinit
vm-121-cloudinit

Regards,
 
Last edited:
does the '--long' command still throw an error?
 

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!