o:dongda...@gmail.com]
> Sent: 02 February 2015 20:14
> To: users@cloudstack.apache.org
> Subject: Re: Force cleaning primary storage.
>
> Hi, Geoff,
> Thanks a lot, here are the details:
> 1. CloudStack version: 4.4.1
> 2. Hypervisor: KVM
> 3. Primary storage is NFS, but s
: +447968161581
geoff.higginbot...@shapeblue.com
-Original Message-
From: Dan Dong [mailto:dongda...@gmail.com]
Sent: 02 February 2015 20:14
To: users@cloudstack.apache.org
Subject: Re: Force cleaning primary storage.
Hi, Geoff,
Thanks a lot, here are the details:
1. CloudStack version: 4.4.1
2
+44 20 3603 0540 | M: +447968161581
>
> geoff.higginbot...@shapeblue.com
>
> -Original Message-
> From: Dan Dong [mailto:dongda...@gmail.com]
> Sent: 02 February 2015 16:12
> To: users@cloudstack.apache.org
> Subject: Force cleaning primary storage.
>
> Hi, All,
>
: users@cloudstack.apache.org
Subject: Force cleaning primary storage.
Hi, All,
I found the primary storages are keep decreasing after I create and then
destroy VMs. Although the VMs are destroyed and expunged, their occupation on
primary storage seems never been released( even after weeks).
Is there
Hi, All,
I found the primary storages are keep decreasing after I create and then
destroy VMs. Although the VMs are destroyed and expunged, their occupation
on primary storage seems never been released( even after weeks).
Is there a way to force releasing the disk space after a VM has been
destro