"List Managed Systems" disk space not accurate

Hi,

I have an issue with Cloudmin not showing accurate info in the "List Managed Systems" page.
How I got to this is I created a new VM following the standard procedure (Create KVM instance), but after that I deleted the LVM attached to it and renamed an older LVM that had an existing installation instead of it... Now Cloudmin only shows 2 GB disk space (the original sistem size) for the VM while the LVM itself is actually 100 GB (actually I have 2 LVMs attached to this VM, none of them are picked up by Cloudmin).
Is it possible to refresh those values based on lvdisplay or smth similar?

Status: 
Closed (fixed)

Comments

So you manually modified the LV, rather than using Cloudmin? If so, you can force it to refresh the cache of disk usage by selecting the VM from the left menu, and clicking "Refresh Fully".

Or you can do it from the command line with the command :

cloudmin refresh-systems --host your-kvm-instance --regenerate

Because computing the size of all LVs on a VM can be slow, Cloudmin caches the total size separately and updates it when you add, remove or resize disks from the UI.

Fair enough; the command line thing is quite sexy. Cheers for that!

Automatically closed -- issue fixed for 2 weeks with no activity.

Hi,

It just happened again. This to a machine that got the disk enlarged from 20 to 40 via cloudmin. List managed systems never updated, not even after 1 week. cloudmin refresh-systems --host your-kvm-instance --regenerate <- this command did the trick again though.

FYI, it's the disk information that doesn't get updated automagically. Bandwidth information for example works just fine.

Was the disk image that was resized in an LVM logical volume, or a regular file?

Also, was the resize done from the web UI or the command line?

Jamie,

It's LVM and the operation hgas been done from cloudmin (web).

OK, I found a 2nd bug that can cause this problem - this one only effects KVM, so I don't notice it the first time around..

The fix will be in Cloudmin 5.6.

Automatically closed -- issue fixed for 2 weeks with no activity.