You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Prasanna Santhanam (JIRA)" <ji...@apache.org> on 2012/12/17 05:04:12 UTC
[jira] [Created] (CLOUDSTACK-649) KVM storage gc does not delete
the invalid snapshots from physical storage
Prasanna Santhanam created CLOUDSTACK-649:
---------------------------------------------
Summary: KVM storage gc does not delete the invalid snapshots from physical storage
Key: CLOUDSTACK-649
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-649
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: KVM, Snapshot
Affects Versions: 4.0.0, 4.0.1
Reporter: Prasanna Santhanam
Assignee: Prasanna Santhanam
When CleanupSnapshotBackupCommand is sent to the SSVM agent because it needs to perform storage GC - outdated snapshots remain undeleted. But the answer returned to mgmt server is success. This is related to CLOUDSTACK-643 where KVM uses a different path to its snapshot backups that includes the zoneid in the path.
Storage GC fails for KVM:
Command sent by mgmt server to ssvm:
2012-12-17 06:06:12,155 DEBUG [agent.transport.Request] (StorageManager-Scavenger-1:null) Seq 11-575012901: Sending { Cmd , MgmtId: 345050870294, via: 11, Ver: v1, Flags: 100011, [{"CleanupSnapshotBackupCommand":{"secondaryStoragePoolURL":"nfs://mysecstorage/export/home/secondary","dcId":3,"accountId":7,"volumeId":31,"validBackupUUIDs":["/snapshots/3/7/31/any_ROOT-29_20121217000221"],"wait":0}}] }
Note: KVM path to snapshot includes the zoneid/accountid/volumeid and not just accountid/volumeid like in the case of XenServer
On the SSVM (with additional warn logs enabled) the response to this command is like follows:
1217:271775:2012-12-17 00:32:41,290 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Request:Seq 11-575012901: { Cmd , MgmtId: 345050870294, via: 11, Ver: v1, Flags: 100011, [{"CleanupSnapshotBackupCommand":{"secondaryStoragePoolURL":"nfs://mysecstorage/export/home/secondary","dcId":3,"accountId":7,"volumeId":31,"validBackupUUIDs":["/snapshots/3/7/31/any_ROOT-29_20121217000221"],"wait":0}}] }
1218-272164-2012-12-17 00:32:41,291 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Processing command: com.cloud.agent.api.CleanupSnapshotBackupCommand
1219-272309-2012-12-17 00:32:41,291 DEBUG [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-4:) Executing: mount
1220-272430-2012-12-17 00:32:41,293 DEBUG [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-4:) Execution is successful.
1221-272558-2012-12-17 00:32:41,295 WARN [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-4:) didn't find parent snapshot directory at /mnt/SecStorage/cbf2a8fe-fa9f-316e-b8de-d1e291869694//snapshots/7/31
1222:272771:2012-12-17 00:32:41,295 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Seq 11-575012901: { Ans: , MgmtId: 345050870294, via: 11, Ver: v1, Flags: 10, [{"Answer":{"result":true,"wait":0}}] }
The warn message shows the path the ssvm is looking for. Inspite of not finding the snapshot path, we proceed with returning a true answer to mgmt server.
--
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