You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Nick Wales (JIRA)" <ji...@apache.org> on 2013/06/07 16:54:19 UTC
[jira] [Created] (CLOUDSTACK-2897) Storage migration has left
volumes on secondary storage
Nick Wales created CLOUDSTACK-2897:
--------------------------------------
Summary: Storage migration has left volumes on secondary storage
Key: CLOUDSTACK-2897
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2897
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: Storage Controller
Affects Versions: 4.0.1
Reporter: Nick Wales
Priority: Critical
I have moved all the VM's and the associated volumes to new storage and this appears to have been a two part copy job on the part of cloudstack:
Primary Storage 1 -> Secondary Storage -> Primary Storage 2
Right now two and three day old copies of the volumes are still resident on the secondary storage taking up hundreds of GB's for no apparent reason.
There is no mention of these volumes in the UI and its way beyond the "storage.cleanup.interval" time. Is there a way to clean them up?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira