mirror of
git://git.proxmox.com/git/qemu-server.git
synced 2025-01-10 01:18:01 +03:00
7585466269
Since an old change released with a version bump on 2009-09-07, we search all enabled storages for VMID maching volumes on VM removal and purge those too. This has multiple pitfalls and may be quite unexpected for some users. It can make problems when: * on recovery a VM is created, before disks are reattached the admin notices some settings issues and chooses to just recreate the VM; but during destroying the dummy VM all related disks get destroyed unconditionally which may result in data loss. This actually happened and is the original reason for the decision to change this. * a storage is shared between PVE instance (between a set of clusters and/or single nodes), while this is against our rules it may still come as a surprise if destroying a VM on node A may destroy unrelated and unreferenced disks on the unrelated node B without asking or allowing to avoid that. As this the removal of matching but unreferenced disks can result in permanent data loss (up to the last backup) and may be to subtle and unforgiving, allow to opt-out of it. In the long run we want to make this opt-in, but that is an API change and so needs to wait for next major release. But, we can adapt the GUI already to make it opt-in there, catching most of the cases. side-note: CT do not have this behavior at all Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com> |
||
|---|---|---|
| .. | ||
| API2 | ||
| CLI | ||
| QemuServer | ||
| VZDump | ||
| Makefile | ||
| QemuConfig.pm | ||
| QemuMigrate.pm | ||
| QemuServer.pm | ||
| QMPClient.pm | ||