Fariborz - just a word of warning - remember all your templates which are in
use will show up as large files in primary storage. If you use linked clones
and wiped the templates you will also loose all the child VMs - so be careful.
You would check the templates on primary storage by cross referencing the
vm_template and template_spool_ref tables.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 31/03/2019, 21:14, "Suresh Kumar Anaparti" <sureshkumar.anapa...@gmail.com>
wrote:
Hi Fariborz,
Fetch the UUIDs of unused volumes with state 'Ready' (either using
*listVolumes* API or DB cmd: "*SELECT * FROM cloud.volumes where
instance_id is NULL and state = 'Ready'*") and delete these volumes with
UUIDs using deleteVolume API.
Before that, make sure the global config "*storage.cleanup.enabled*" is
enabled. Also, set the global config "*storage.cleanup.delay*" to smaller
interval before deleting volumes so that all the destroyed volumes are
expunged immediately and then revert back to original after few expunge
cycles.
- Suresh
On Mon, Apr 1, 2019 at 12:51 AM Fariborz Navidan <mdvlinqu...@gmail.com>
wrote:
> Hello,
>
> It looks lie that there are unused volumes files with large size let in
> primary storage. Is there any way to safely delete them and free up space?
>
> Thanks
>
dag.sonst...@shapeblue.com
www.shapeblue.com
Amadeus House, Floral Street, London WC2E 9DPUK
@shapeblue
