Resize of VDisk failing to show inside VM
There have been a number of tickets related to disk geometry not being reflected after a resize in the VM, although the VDisk is reported as larger and the CP shows the larger VDisk.
VM fdisk -l /dev/vda still shows old size.
To fix this:
onappstore diskinfo uuid=<VDUUID> - where VDUUID is the VDisk ID that is not being reported correctly in the VM
Capture all the (backend) members:
onappstore nodeinfo uuid=<memberid> #From above
telnet <backend_ip> #From above
There should be one file referring to <VDUUID>. The others are possibly stale snapshot refs.
onappstore diskinfo uuid=<snap_uuid> #If it still exists, then we shouldn't resize / cannot resize with snapshot. Otherwise, the vdisks should not be found.
Delete these reference files.
Once done for all backend nodes for all vdisks that are affected for that VM, it will be necessary to offline and online the VDisk. The safest way to do this if it is a primary disk is to ask the client if it is possible to restart the VM to reflect the change. Confirm with the client afterwards that Vdisk resize worked.
This is due to stale refcount for snapshots.