cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhinandan Prateek (JIRA)" <>
Subject [jira] [Updated] (CLOUDSTACK-2897) Storage migration has left volumes on secondary storage
Date Sat, 03 Aug 2013 01:49:49 GMT


Abhinandan Prateek updated CLOUDSTACK-2897:

    Fix Version/s: 4.2.0
> Storage migration has left volumes on secondary storage
> -------------------------------------------------------
>                 Key: CLOUDSTACK-2897
>                 URL:
>             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
>            Assignee: Nitin Mehta
>            Priority: Critical
>              Labels: secondary, storage
>             Fix For: 4.2.0
> 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:

View raw message