This is fixed as part of CLOUDSTACK-3445 in master and 4.2. The issue was with local storage pool used bytes getting wrongly stored as you noted.
-Koushik > -----Original Message----- > From: Mike Tutkowski [mailto:[email protected]] > Sent: Tuesday, July 16, 2013 6:46 AM > To: [email protected] > Subject: Re: Is VMware working in 4.2? > > Yeah, it appears to be completely backwards. > > When I go to the dashboard, it says I've got 34.05 GB used of 35 GB. In > reality > 34.05 are available (per what vSphere Client says). > > I can log a bug on this. > > > On Mon, Jul 15, 2013 at 7:00 PM, Mike Tutkowski < > [email protected]> wrote: > > > Hi, > > > > I was having a hard time understanding why my VMware-only setup was > > complaining that there was little space left on my one primary storage > > until I looked in the DB. > > > > 36562796544 (below) supposedly represents the used bytes while > > 37580963840 (also below) represents the capacity bytes. > > > > Used bytes was recently changed from available bytes (in late June for > > 4.2) and I wonder if this was not incorporated into the VMware logic > > because the datastore that this DB row represents claims (in vSphere > > Client) have have over 34 GB remaining. > > > > 6 172.16.140.2 Local Storage 4cccd1e4d37c3afc94381b7d3a914757 LVM 0 1 > > 1 3 > > 36562796544 37580963840 172.16.140.2 datastore-74 2013-07-16 00:37:11 > > Up DefaultPrimary HOST 0 > > > > Thoughts? > > > > -- > > *Mike Tutkowski* > > *Senior CloudStack Developer, SolidFire Inc.* > > e: [email protected] > > o: 303.746.7302 > > Advancing the way the world uses the > > cloud<http://solidfire.com/solution/overview/?video=play> > > *(tm)* > > > > > > -- > *Mike Tutkowski* > *Senior CloudStack Developer, SolidFire Inc.* > e: [email protected] > o: 303.746.7302 > Advancing the way the world uses the > cloud<http://solidfire.com/solution/overview/?video=play> > *(tm)*
