TASK ERROR: rbd error: rbd: listing images failed

[dcsapak]

can you please provide the output of both commands again? (with '--long' and without) ?
i doubt you currently get the *same* error if you deleted the image

 

[powersupport]

Sure, the error is same, please see below

# 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 7.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
vm-124-cloudinit 4 MiB 2
vm-124-disk-0 10 GiB 2
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

 

[dcsapak]

hi,

can you post the output of

rbd -p <pool> info <disk image>

for each of the "missing" images?

 

[powersupport]

rbd -p satapx-storage info vm-127-disk-0
rbd: error opening image vm-127-disk-0: (2) No such file or directory
rbd -p satapx-storage info vm-122-disk-0
rbd: error opening image vm-122-disk-0: (2) No such file or directory
rbd -p satapx-storage info vm-124-disk-0
rbd: error opening image vm-124-disk-0: (2) No such file or directory

I also noticed the VM 124 was showing in disk image details, then I went to terminate the vm
Removing image: 94% complete...
Removing image: 95% complete...
Removing image: 96% complete...
Removing image: 97% complete...
Removing image: 98% complete...
Removing image: 99% complete...
Removing image: 100% complete...done.
TASK ERROR: rbd error: rbd: listing images failed: (2) No such file or directory

No, the image is missing and VM cannot be removed, it seems like a bug in the system

Please advice

Thank you

 

[powersupport]

Hi,

Anyone can advise on this?

Thank you

 

[powersupport]

Hi,

I could see there are proxmox updates available in the server, may I know if the upgrade could resolve the issue?

Thank you

 

[dcsapak]

as i wrote before, i'd try removing the "ghost" images with 'rbd rm' so that the image listing can succeed..

 

[powersupport]

Hi,

We are facing the issue in the front end of the proxmox, could you please assist to let us know why this error occurs and how to resolve the issue so that we can remove the VM from the front end.

could you please assist to resolve this issue?

Thank you.

 

[Papabearactual]

Hi,

Pardon me for reviving an older thread but I ran into this problem and found a solution, so, thought I'd share for posterity.

The first time I tried to remove the CT and failed with.

2022-09-02T20:36:44.922-0700 7f9435cb0700 -1 librbd::image::PreRemoveRequest: 0x5640a98dd730 check_image_watchers: image has watchers - not removing
Removing image: 0% complete...failed.
rbd: error: image still has watchers
TASK ERROR: rbd rm 'vm-111-disk-0' error: rbd: error: image still has watchers

Subsequent attempts to remove the CT failed with.

TASK ERROR: rbd error: rbd: error opening image vm-111-disk-0: (2) No such file or directory

To resolve, verify the image is gone (not sure if this scenario could happen but doesn't hurt to verify ) rbd ls POOLNAME where POOLNAME is the name of the pool in proxmox. Remove if it exists. Then just remove the conf file from proxmox. rm /etc/pve/lxc/CTNUM.conf where CTNUM is the container number.

Happy proxmox'ing fellow googlers!