Hello,
We are using a Proxmox (3 nodes) - Ceph (6 nodes) infrastructure as independent storage for Proxmox.
After updating the Proxmox servers and rebooting them, it seems we no longer have access to a Ceph storage pool. VMs hosted on this disk pool (RDB) no longer boot. At the boot, VM hang when thy acces to storage.
Actually we use :
proxmox-ve: 8.3.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300
On Ceph nodes , we have :
[root@clrcephnode01 ~]# ceph -v
ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy (stable)
root@clrproxmox14:/etc/pve/qemu-server# rbd ls -p EspaceInfo --long
rbd: error opening vm-110-disk-0: (2) No such file or directory
NAME SIZE PARENT FMT PROT LOCK
vm-100-disk-0 80 GiB 2 excl
vm-101-disk-0 150 GiB 2 excl
vm-102-disk-0 40 GiB 2 excl
vm-103-disk-0 32 GiB 2 excl
vm-104-disk-0 132 GiB 2 excl
vm-105-disk-0 65 GiB 2 excl
vm-105-disk-0@snapshot-clrarcce03-13082024 65 GiB 2
vm-105-state-snapshot-clrarcce03-13082024 2.8 GiB 2
vm-106-disk-0 45 GiB 2 excl
vm-106-disk-0@snapshot-clrhtcmgtb-13Aout2024 45 GiB 2
vm-106-state-snapshot-clrhtcmgtb-13Aout2024 1.6 GiB 2
vm-107-disk-0 750 GiB 2 excl
vm-107-disk-0@snapshot-clrwn001-14Aout2024 750 GiB 2
vm-107-state-snapshot-clrwn001-14Aout2024 38 GiB 2
vm-108-disk-0 750 GiB 2 excl
vm-109-disk-0 750 GiB 2 excl
vm-110-disk-1 750 GiB 2 excl
vm-111-disk-0 750 GiB 2 excl
vm-112-disk-0 750 GiB 2 excl
vm-113-disk-0 100 GiB 2
vm-114-disk-0 100 GiB 2
vm-115-disk-0 60 GiB 2 excl
vm-125-disk-0 200 GiB 2 excl
rbd: listing images failed: (2) No such file or directory
Perhaps it is related;
Any idea are welcome.
Tanks
Best regard
Jean-claude
We have such error :
We are using a Proxmox (3 nodes) - Ceph (6 nodes) infrastructure as independent storage for Proxmox.
After updating the Proxmox servers and rebooting them, it seems we no longer have access to a Ceph storage pool. VMs hosted on this disk pool (RDB) no longer boot. At the boot, VM hang when thy acces to storage.
Actually we use :
proxmox-ve: 8.3.0 (running kernel: 6.8.12-9-pve)
pve-manager: 8.3.5 (running version: 8.3.5/dac3aa88bac3f300
On Ceph nodes , we have :
[root@clrcephnode01 ~]# ceph -v
ceph version 17.2.7 (b12291d110049b2f35e32e0de30d70e9a4c060d2) quincy (stable)
root@clrproxmox14:/etc/pve/qemu-server# rbd ls -p EspaceInfo --long
rbd: error opening vm-110-disk-0: (2) No such file or directory
NAME SIZE PARENT FMT PROT LOCK
vm-100-disk-0 80 GiB 2 excl
vm-101-disk-0 150 GiB 2 excl
vm-102-disk-0 40 GiB 2 excl
vm-103-disk-0 32 GiB 2 excl
vm-104-disk-0 132 GiB 2 excl
vm-105-disk-0 65 GiB 2 excl
vm-105-disk-0@snapshot-clrarcce03-13082024 65 GiB 2
vm-105-state-snapshot-clrarcce03-13082024 2.8 GiB 2
vm-106-disk-0 45 GiB 2 excl
vm-106-disk-0@snapshot-clrhtcmgtb-13Aout2024 45 GiB 2
vm-106-state-snapshot-clrhtcmgtb-13Aout2024 1.6 GiB 2
vm-107-disk-0 750 GiB 2 excl
vm-107-disk-0@snapshot-clrwn001-14Aout2024 750 GiB 2
vm-107-state-snapshot-clrwn001-14Aout2024 38 GiB 2
vm-108-disk-0 750 GiB 2 excl
vm-109-disk-0 750 GiB 2 excl
vm-110-disk-1 750 GiB 2 excl
vm-111-disk-0 750 GiB 2 excl
vm-112-disk-0 750 GiB 2 excl
vm-113-disk-0 100 GiB 2
vm-114-disk-0 100 GiB 2
vm-115-disk-0 60 GiB 2 excl
vm-125-disk-0 200 GiB 2 excl
rbd: listing images failed: (2) No such file or directory
Perhaps it is related;
Any idea are welcome.
Tanks
Best regard
Jean-claude
We have such error :