VM doesnt recognize new rbd disk size

immo

Renowned Member
Nov 20, 2014
92
0
71
I resized as usual the rbd disk via GUI (remote ceph storage) from 170G to 800G but the new size is not recognized from the linux. Also partprobe doesnt help.
lsblk and fdisk always show still the old size.
But pvesm shows the right new size.
A vm reboot is not possible due to ongoing work which is not allowed to interrupt from the client.
Any ideas how to bring the right disk size into the vm ?

The vm has to snapshots with RAM and two more without.
 
Last edited:
Its possible for Kernel, due to a bug or some other circumstance, to miss the disk change event. How you can recover from it depends on many other factors, one of them being the controller on which this disk sits. It can also depend on the OS and Kernel versions of both hypervisor and the VM. Without any technical details the best I can advise is to plug something like this into google "resized disk in linux vm not showing" and review the few troubleshooting guides that come up, i.e.: https://codenotary.com/blog/enlarge-a-disk-and-partition-of-any-linux-vm-without-a-reboot/

If its still not working - come back with more details, like command outputs, and someone might be able to provide additional help.


Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
hi pvesm show now wrong data

root@prox01:~# pvesm status
Name Type Status Total Used Available %
ISOs nfs active 5325332480 3041432576 2015448064 57.11%
ceph-nfs nfs active 120023547904 77196648448 42826899456 64.32%
data rbd active 9786533294 11408814 9775124480 0.12%
local dir active 304345408 64708 304264316 0.02%
proxmox rbd active 9775126750 2270 9775124480 0.00%

but the majority our vms are running on rbd proxmox

and pvesm list proxmox failed in the meantime

root@prox01:~# pvesm list proxmox
rbd error: rbd: listing images failed: (2) No such file or directory

root@prox01:~# pvesm list data
works fine

root@prox22:/etc/pve/nodes/prox05/qemu-server# more 317.conf agent: 1 balloon: 8196 boot: cdn bootdisk: ide0 cores: 16 cpu: host ide0: proxmox:vm-317-disk-0,discard=on,size=500G,ssd=1 ide2: none,media=cdrom memory: 163840 name: GLUE-MCP2-SCALE-BNG500-22.201 net0: virtio=F6:E1:EE:49:DC:B0,bridge=vmbr9001,tag=222 numa: 0 onboot: 0 ostype: l26 parent: Done225OLTs scsihw: virtio-scsi-pci smbios1: uuid=43e56d1a-c59c-40cb-96ef-628b8681a76b sockets: 1

several snapshots existing with and without RAM

and
rbd -p proxmox -m 10.160.253.101,10.160.253.105,10.160.253.107 -n client.proxmox_ceph --keyring /etc/pve/priv/ceph/proxmox.keyring ls

works and I see the vm images
 
Last edited:

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!