Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Fri, 7 Jun 2013 14:54:19 +0000 (UTC)
From: "Nick Wales (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12651708.1370616777683.84881.1370616859919@arcas>
In-Reply-To: <JIRA.12651708.1370616777683@arcas>
References: <JIRA.12651708.1370616777683@arcas>
Subject: [jira] [Created] (CLOUDSTACK-2897) Storage migration has left
 volumes on secondary storage
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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