Snapshots as volume chains problem

iwik

Active Member
Oct 7, 2021
77
16
28
43
I have setup one PVE host with one LUN from SAN and users are testing Snapshots as Volume-Chain feature.

Then have broken it - they are QA, so it is their job.

There are no snapshots on vm:

Code:
root@pve04:~# qm listsnapshot 104
`-> current                                             You are here!

But when I try to do one:

Code:
snapshotting 'drive-ide0' (SAN14l99:vm-104-disk-1.qcow2)
external qemu snapshot
Creating a new current volume with test as backing snap
Renamed "vm-104-disk-1.qcow2" to "snap_vm-104-disk-1_test.qcow2" in volume group "SAN14l99"
Rounding up size to full physical extent <100.02 GiB
Logical volume "vm-104-disk-1.qcow2" created.
Formatting '/dev/SAN14l99/vm-104-disk-1.qcow2', fmt=qcow2 cluster_size=131072 extended_l2=on preallocation=metadata compression_type=zlib size=107374182400 backing_file=snap_vm-104-disk-1_test.qcow2 backing_fmt=qcow2 lazy_refcounts=off refcount_bits=16
blockdev replace current by test
snapshot create failed: starting cleanup
TASK ERROR: VM 104 qmp command 'blockdev-reopen' failed - Failed to find node with node-name='drive-ide0'

But from lvs, there are some snapshots on vm 104:

Code:
# lvs
  LV                              VG       Attr       LSize    Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  snap_vm-103-disk-0_init.qcow2   SAN14l99 -wi-a-----    4.00m
  snap_vm-103-disk-1_init.qcow2   SAN14l99 -wi-a----- <100.02g
  snap_vm-104-disk-1_backup.qcow2 SAN14l99 -wi-ao---- <100.02g
  snap_vm-104-disk-1_clean.qcow2  SAN14l99 -wi-ao---- <100.02g
  vm-100-disk-0.qcow2             SAN14l99 -wi-a----- <100.02g
  vm-100-disk-1.qcow2             SAN14l99 -wi-a-----    4.00m
  vm-100-disk-2                   SAN14l99 -wi-------    4.00m
  vm-103-disk-0.qcow2             SAN14l99 -wi-a-----    4.00m
  vm-103-disk-1.qcow2             SAN14l99 -wi-a----- <100.02g
  vm-104-disk-0.qcow2             SAN14l99 -wi-ao----    4.00m
  vm-104-disk-1.qcow2             SAN14l99 -wi-a----- <100.02g

Code:
root@pve04:/etc/pve/qemu-server# cat 104.conf
agent: 1,fstrim_cloned_disks=1
bios: ovmf
boot: order=ide0;ide2;net0
cores: 2
cpu: x86-64-v2-AES
efidisk0: SAN14l99:vm-104-disk-0.qcow2,efitype=4m,pre-enrolled-keys=1,size=528K
ide0: SAN14l99:vm-104-disk-1.qcow2,size=100G
ide2: none,media=cdrom
machine: pc-q35-9.2+pve1
memory: 4096
meta: creation-qemu=9.2.0,ctime=1751972183
name: modtest-2
net0: e1000=BC:24:11:16:15:E8,bridge=VLAN126,firewall=1
numa: 0
ostype: win11
scsihw: virtio-scsi-single
smbios1: uuid=8027b995-9d96-4c45-84db-6be83e8952cc
sockets: 1
tags: template
vmgenid: 8606c20e-9011-48f7-bbeb-4b9b48c0601f

So question is, how to fix it now?
 
Last edited: