As per 4.6 docs, storage overprovisioning is only supported with NFS when using 
XenServer, refer 
http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.6/choosing_deployment_architecture.html.

I have not come across a feature request for implementing this feature for 
local storage. In case you wish to raise one then please do so here, 
https://issues.apache.org/jira/browse/CLOUDSTACK/. Note, please double check if 
one already exists.

Regards,
Somesh


-----Original Message-----
From: ilya [mailto:ilya.mailing.li...@gmail.com] 
Sent: Monday, February 01, 2016 2:50 PM
To: users@cloudstack.apache.org
Subject: Re: overprovisioning of local storage

Its a bug that was fixed in latest 4.5

On 2/1/16 2:22 AM, S. Brüseke - proIO GmbH wrote:
> Hi,
> 
> we are using CS 4.4.0 and it looks like we are unable to overprovisioning 
> local storage. We configured storage.overprovisioning.factor with 4 and using 
> ext local storage on XenServer pools. Is this a known limitation/bug? And if 
> so does anybody know if this has been fixed in newer versions?
> 
> Thanks for any help and clarification on this!
> 
> Mit freundlichen Grüßen / With kind regards,
> 
> Swen
> 
> 
> 
> 
> - proIO GmbH -
> Geschäftsführer: Swen Brüseke
> Sitz der Gesellschaft: Frankfurt am Main
> 
> USt-IdNr. DE 267 075 918
> Registergericht: Frankfurt am Main - HRB 86239
> 
> Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte 
> Informationen. 
> Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich 
> erhalten haben, 
> informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
> Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht 
> gestattet. 
> 
> This e-mail may contain confidential and/or privileged information. 
> If you are not the intended recipient (or have received this e-mail in error) 
> please notify 
> the sender immediately and destroy this e-mail.  
> Any unauthorized copying, disclosure or distribution of the material in this 
> e-mail is strictly forbidden. 
> 
> 

Reply via email to