[
https://issues.apache.org/jira/browse/CLOUDSTACK-9022?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15035572#comment-15035572
]
ASF GitHub Bot commented on CLOUDSTACK-9022:
--------------------------------------------
Github user ustcweizhou commented on the pull request:
https://github.com/apache/cloudstack/pull/1145#issuecomment-161243997
@wilderrodrigues I just tested.
I set the storage.cleanup.interval to 60s, the storage.cleanup.delay to
120s.
I restored a VM, then the old volume of the vm will be in 'Destroy' state
```
mysql> select id,name,uuid,created,updated,removed,state from volumes where
id=7574\G
*************************** 1. row ***************************
id: 7574
name: ROOT-7558
uuid: 82c5991d-5211-4fd8-bd8b-f1285cc50574
created: 2015-11-30 08:27:36
updated: 2015-12-02 09:50:34
removed: NULL
state: Destroy
1 row in set (0.00 sec)
```
The volume is expunged after 2-3 minutes.
```
mysql> select id,name,uuid,created,updated,removed,state from volumes where
id=7574\G
*************************** 1. row ***************************
id: 7574
name: ROOT-7558
uuid: 82c5991d-5211-4fd8-bd8b-f1285cc50574
created: 2015-11-30 08:27:36
updated: 2015-12-02 09:53:31
removed: 2015-12-02 09:53:31
state: Expunged
1 row in set (0.00 sec)
```
> We should keep Destroyed volumes for some time
> ----------------------------------------------
>
> Key: CLOUDSTACK-9022
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9022
> Project: CloudStack
> Issue Type: Improvement
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Wei Zhou
> Assignee: Wei Zhou
>
> for now, the Destroyed volumes will be expunged in Storage cleanup thread, no
> matter when they are destroyed.
> In Expunging vm, we only clean the Destroyed vms which have been destroyed at
> least 'expunge.delay' seconds.
> We need to add the similar configuration for volumes.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
