GitHub user nickaccuweb added a comment to the discussion: Orphaned snapshots 
remain after deleting volumes in CLVM_NG primary storage

@mbertolina 

I checked the CloudStack 4.23 documentation, and this appears to be expected 
behavior.

CloudStack treats volumes and their snapshots as separate resources. Deleting a 
volume does not automatically delete its snapshots, as they may still be needed 
to restore data or create another volume.

The same behavior was reported in GitHub issue #14154, where a CloudStack 
contributor confirmed that snapshots are expected to remain available after the 
original volume is deleted. The issue was subsequently marked as not a bug.

Since you've confirmed that the underlying LVM volumes are being removed 
correctly, I would suggest checking whether the remaining snapshot is still 
available on secondary storage or its configured backup location.

Could you try creating a new volume from that snapshot after deleting the 
original volume?

If the new volume is created successfully, the behavior is consistent with 
CloudStack's snapshot lifecycle. You can then delete the snapshot separately 
from the Volume Snapshots section when it is no longer required.

However, if the snapshot cannot be restored or causes errors because the 
original volume no longer exists, that would indicate a separate issue worth 
investigating.

Reference:
https://github.com/apache/cloudstack/issues/14154

https://docs.cloudstack.apache.org/en/latest/adminguide/storage.html#volume-deletion-and-garbage-collection

Nick R 
AccuWeb.Cloud

GitHub link: 
https://github.com/apache/cloudstack/discussions/14437#discussioncomment-19466170

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: [email protected]

Reply via email to