Skip to content
This repository has been archived by the owner on Jul 25, 2023. It is now read-only.

Datastore Actual Usage incorrect #17

Open
mgen50 opened this issue Aug 31, 2017 · 10 comments
Open

Datastore Actual Usage incorrect #17

mgen50 opened this issue Aug 31, 2017 · 10 comments
Assignees

Comments

@mgen50
Copy link

mgen50 commented Aug 31, 2017

The datastore actual usage is being reported incorrectly. In ManageIQ I see the following:

2017-08-31_11h25_32

In SCVMM if I look at the disk allocated field, that VM is reporting 74 GB.

My base disk is thin to begin with so the actual usage shown under Disks should not be reported as 50GB but rather the real value on disk (if this info is available to get in SCVMM)

@davidlacasse
Copy link

davidlacasse commented Aug 31, 2017

I don't know if it's related but the vmware-provider seems to have a similar issue ManageIQ/manageiq-providers-vmware#98. The Snapshots field also reporting a wrong value (always 0 no matter how many snapshot we have).

I don't know if someone have a workaround to get the information right.

Thanks,

@djberg96
Copy link
Collaborator

@mgen50 When I look at what SCVMM is showing me under the "Storage" tab and look at "Total Capacity" and "Available Capacity" for a VM versus what ManageIQ is showing me, the values appear to line up.

Can you please take a snapshot from SCVMM that shows the VM in question versus what you're seeing in ManageIQ? Perhaps you're expecting a different property?

@mgen50
Copy link
Author

mgen50 commented Aug 31, 2017

Hi @djberg96,

In SCVMM I see this in the VMs and Services view:

image

If I check the properties of the vm and look at the hard drive, I see this

image

I don't understand why the currently expanded thing says only 0.01GB though since I see it's using about 36GB on disk when i verify manually.

This VM has checkpoints so if i check the properties on the checkpoint and look at the disk usage there, I see something more along the lines of what i expect to see:

image

I think what's happening is that when there's a checkpoint, under the hardware config section the value showing for drive space is nonsense and the real values are coming from the same section under the properties of the checkpoint (which might explain that 4MB value in my original post)

Under the properties view for the vm, my storage section doesn't have anything

image

I also have a similar issue with vmware and it seems to be pretty close to the issue Lhuk pointed out.

@djberg96
Copy link
Collaborator

@agrare Any thoughts on this? I never had time to dig into it.

@agrare
Copy link
Member

agrare commented Mar 29, 2018

This looks like it is correct when there aren't any checkpoints on the VM, I still have to test with a VM that has a checkpoint

@miq-bot miq-bot added the stale label Oct 1, 2018
@miq-bot
Copy link
Member

miq-bot commented Oct 1, 2018

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

@JPrause
Copy link
Member

JPrause commented Jan 30, 2019

@agrare should this issue remain open. If yes, can you remove the stale label. Otherwise please close the issue. If there's no update by next week, I'll be closing this issue.

@agrare agrare added pinned and removed stale labels Jan 30, 2019
@paltaa
Copy link

paltaa commented Feb 19, 2019

Is there a fix to this? or any workaround?

@agrare
Copy link
Member

agrare commented Feb 19, 2019

Not yet

@dmetzger57
Copy link

@chessbyte chessbyte removed the pinned label Aug 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants