PVE 4.4-1/eb2d6f1e
I tried to rollback a snapshot (id 505) and it failed saying "disk threshold reached, not going to create a new volume" or somesuch...
I deleted other unused VMs and deleted snapshots from other VMs to make space. VM 505 was still locked so I used the shell qm unlock utility to try to start or continue with rollback. I've rebooted the proxmox server as well in case this was needed for the filesystem to see the available disk resources.
It seems that in the roll back, vm505 has unreferenced the lvm partitions it disks were pointing to and when I try to rollback or start it does not have a base reference point.
lvremove 'pve/vm-505-disk-1' error: Failed to find logical volume "pve/vm-505-disk-1"
Does anyone know how to manually remap these lvm volumes so I can get it to run? As you can see form the output of two lvdisplay commands below, vm-505-disk-1 is here but only as a snapshot. I would guess that the rollback operation unlinked disk-, but disk-1 shows below because it never got that far.
root@maz-pve58:/dev/pve# lvdisplay|grep vm-505-disk-2
LV Path /dev/pve/vm-505-disk-2
LV Name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s1
LV Name snap_vm-505-disk-2_s1
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s2
LV Name snap_vm-505-disk-2_s2
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s3
LV Name snap_vm-505-disk-2_s3
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s4
LV Name snap_vm-505-disk-2_s4
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s5
LV Name snap_vm-505-disk-2_s5
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s6
LV Name snap_vm-505-disk-2_s6
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s7
LV Name snap_vm-505-disk-2_s7
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s8
LV Name snap_vm-505-disk-2_s8
LV Thin origin name vm-505-disk-2
root@maz-pve58:/dev/pve# lvdisplay|grep vm-505-disk-1
LV Path /dev/pve/snap_vm-505-disk-1_s1
LV Name snap_vm-505-disk-1_s1
LV Path /dev/pve/snap_vm-505-disk-1_s2
LV Name snap_vm-505-disk-1_s2
LV Path /dev/pve/snap_vm-505-disk-1_s3
LV Name snap_vm-505-disk-1_s3
LV Path /dev/pve/snap_vm-505-disk-1_s4
LV Name snap_vm-505-disk-1_s4
LV Path /dev/pve/snap_vm-505-disk-1_s5
LV Name snap_vm-505-disk-1_s5
LV Path /dev/pve/snap_vm-505-disk-1_s6
LV Name snap_vm-505-disk-1_s6
LV Path /dev/pve/snap_vm-505-disk-1_s7
LV Name snap_vm-505-disk-1_s7
LV Path /dev/pve/snap_vm-505-disk-1_s8
LV Name snap_vm-505-disk-1_s8
I tried to rollback a snapshot (id 505) and it failed saying "disk threshold reached, not going to create a new volume" or somesuch...
I deleted other unused VMs and deleted snapshots from other VMs to make space. VM 505 was still locked so I used the shell qm unlock utility to try to start or continue with rollback. I've rebooted the proxmox server as well in case this was needed for the filesystem to see the available disk resources.
It seems that in the roll back, vm505 has unreferenced the lvm partitions it disks were pointing to and when I try to rollback or start it does not have a base reference point.
lvremove 'pve/vm-505-disk-1' error: Failed to find logical volume "pve/vm-505-disk-1"
Does anyone know how to manually remap these lvm volumes so I can get it to run? As you can see form the output of two lvdisplay commands below, vm-505-disk-1 is here but only as a snapshot. I would guess that the rollback operation unlinked disk-, but disk-1 shows below because it never got that far.
root@maz-pve58:/dev/pve# lvdisplay|grep vm-505-disk-2
LV Path /dev/pve/vm-505-disk-2
LV Name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s1
LV Name snap_vm-505-disk-2_s1
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s2
LV Name snap_vm-505-disk-2_s2
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s3
LV Name snap_vm-505-disk-2_s3
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s4
LV Name snap_vm-505-disk-2_s4
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s5
LV Name snap_vm-505-disk-2_s5
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s6
LV Name snap_vm-505-disk-2_s6
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s7
LV Name snap_vm-505-disk-2_s7
LV Thin origin name vm-505-disk-2
LV Path /dev/pve/snap_vm-505-disk-2_s8
LV Name snap_vm-505-disk-2_s8
LV Thin origin name vm-505-disk-2
root@maz-pve58:/dev/pve# lvdisplay|grep vm-505-disk-1
LV Path /dev/pve/snap_vm-505-disk-1_s1
LV Name snap_vm-505-disk-1_s1
LV Path /dev/pve/snap_vm-505-disk-1_s2
LV Name snap_vm-505-disk-1_s2
LV Path /dev/pve/snap_vm-505-disk-1_s3
LV Name snap_vm-505-disk-1_s3
LV Path /dev/pve/snap_vm-505-disk-1_s4
LV Name snap_vm-505-disk-1_s4
LV Path /dev/pve/snap_vm-505-disk-1_s5
LV Name snap_vm-505-disk-1_s5
LV Path /dev/pve/snap_vm-505-disk-1_s6
LV Name snap_vm-505-disk-1_s6
LV Path /dev/pve/snap_vm-505-disk-1_s7
LV Name snap_vm-505-disk-1_s7
LV Path /dev/pve/snap_vm-505-disk-1_s8
LV Name snap_vm-505-disk-1_s8
