Disk Space Capacity does not match VM Disk Space Configuration

[ez12a323]

Hey All,

Have a question on how Total Disk Capacity is configured.

I'm not sure where it's getting 13.52 GB for disk space when the Disk space under "Further analysis" is 1.43TB (correct total amount among all of the VM's hard disks). How is this calculated? How does vROPS pick which disk/file system to report on? Does it only report on "sda" or hard disk 1 which is a 20GB disk?

edit:

It's not consistent either. Here's another VM in our environment with a 20GB Hard Disk 1 with 52.77GB configured. It has a DIsk 2 of 100 GB, Disk 3 of 100GB, and disk 4 of 40GB.

[JimKnopf99]

Hi,

thats curious. I double check that in my environment and it is showing me the correct size of the total configured disk space. But it seems, that this is only working on windows vm´s. Could you check that?

On Linux, i have the same differences than you have.

On linux, it looks like this metric is the "total guest file system capacity". If you check the size in the "all metric" Tab, than i guess you will see that those two values are identical.

But that is not the configured size of all disks.

Instead of that metric it should use the "Provisioned Space for VM (GB) under Disk Space.

What Version of vrealize are you using? We are on 6.5

Frank

[MichaelRyom]

I can not replicate the issue. You should open a case with GSS. Might be an underlying problem

[ez12a323]

Are you seeing the correct capacity calculations for Linux based VMs? This seems to be limited to CentOS in our environment.

[ez12a323]

We're on 6.2.1.3774215

[JimKnopf99]

There is something really wrong. In our environment the wrong calculation is all based on linux VM´s.

SUSE or CenOS, RedHat or Oracle.

I found also VM´s that are only showing a questionmark (CentOS).

Until now, i did not found any Windows VM´s showing that issue.

Frank