could you please post your log here ?
It could just be a formatting issue when logging the value. What configs do
you have on the parameters that I talked about previously?


On Thu, Apr 17, 2014 at 1:34 PM, Abu Bashiri <[email protected]>wrote:

> But why an enhancement request? For me it looks like I run into a bug? The
> storage allocation is defiantly not 7627580.872342288 percentage...
>
> -----Ursprüngliche Nachricht-----
> Von: ilya musayev [mailto:[email protected]]
> Gesendet: Donnerstag, 17. April 2014 17:21
> An: [email protected]
> Betreff: Re: AW: Cloudstack complains about storage space
>
> Abu
>
> If this makes no sense - and i agree with you, perhaps you can help the
> project and open enhancement request.
>
> Thanks
> ilya
> On 4/17/14, 9:18 AM, Abu Bashiri wrote:
> > Thanks raphael,
> >
> > but i already know that. Again, for me the value make no sense:
> >
> > since its allocated percentage: 7627580.872342288 since its allocated
> > percentage: 7627580.872342288
> >
> > nsufficient un-allocated capacity on: 3 for volume allocation:
> > [Vol[204|vm=182|ROOT]] since its allocated percentage:
> > 7627580.872342288 has crossed the allocated pool.storage.alloca
> >
> > -----Ursprüngliche Nachricht-----
> > Von: Rafael Weingartner [mailto:[email protected]]
> > Gesendet: Montag, 14. April 2014 14:18
> > An: [email protected]
> > Betreff: Re: Cloudstack complains about storage space
> >
> > Allocation is different from real storage usage.
> >
> > I would to two things:
> >
> > First of all, change you storage.overprovisioning.factor for storage
> allocation to a higher degree such as 5.
> >
> > Second of all, I would change
> > “pool.storage.allocated.capacity.disablethreshold” and
> “pool.storage.capacity.disablethreshold” to something like 90% or even 95%.
> >
> > Cs monitors those values and will just instantiate new VMs if the
> threasholds have not been crossed.
> >
>
>


-- 
Rafael Weingärtner

Reply via email to