Comment 2 for bug 970409
Revision history for this message
| Fergal Mc Carthy (fergal-mccarthy) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
f33e652
(Get the code!)
Bug #1023768 may not truly be a duplicate of this issue.
Let's see if I can summarise my understanding of things:
This bug appears to be about making it a configurable option as to whether it is permitted to attempt to delete a volume that has associated snapshots.
And the subsequent discussion here seems to suggest that it is not necessarily needed as a configurable but instead should be left to the underlying back ends to gracefully decline the deletion of a volume if they don't support doing so when there are associated snapshots
One the other hand bug #1023768 appears to be about whether it is possible for a snapshot to exist independently of the volume it originates from, and as things stand that doesn't appear to be possible because some of the information needed to access a snapshot exists only in the originating volume's entry in the volumes table.
Fergal.