sorry, wrong solution.. but still relevant issue you may encounter
On 3/10/15 11:59 PM, ilya musayev wrote:
fixed in 4.4, but i'd go with 4.5
https://issues.apache.org/jira/browse/CLOUDSTACK-7752
On 3/10/15 6:47 AM, Wido den Hollander wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
fixed in 4.4, but i'd go with 4.5
https://issues.apache.org/jira/browse/CLOUDSTACK-7752
On 3/10/15 6:47 AM, Wido den Hollander wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've ran into the issue where it seems that local storage can't be
overprovisioned.
storage.overprovisioni
It's been brought up quite a few times, actually. I think the reason
it hasn't been fixed yet is that the "right" fix is to make the
storage driver decide if it can do overprovision in a given situation,
which is a bit more work than just slapping together a long 'if'
statement.
On Tue, Mar 10, 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 03/10/2015 02:50 PM, Andrija Panic wrote:
> Nice question - I would like this fixed if possible...?
>
I created a Jira issue for this:
https://issues.apache.org/jira/browse/CLOUDSTACK-8313
> On 10 March 2015 at 14:47, Wido den Hollander
> wrot
Nice question - I would like this fixed if possible...?
On 10 March 2015 at 14:47, Wido den Hollander wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi,
>
> I've ran into the issue where it seems that local storage can't be
> overprovisioned.
>
> storage.overprovisioning.factor is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I've ran into the issue where it seems that local storage can't be
overprovisioned.
storage.overprovisioning.factor is set to 1.5 in both the global and
zone settings, but this is ignored.
In this case it's a 1TB SSD which currently has 68GB all
