snapshot + lvm

[Kosh]

There's a LVM + snapshots. This is a partition connected via SAN.
The VM has a snapshot, but for some reason I can't delete it.

delete qemu external snapshot

delete first snapshot upd

block-commit current to base:upd

commit-drive-scsi1: transferred 63.6 MiB of 962.3 GiB (0.01%) in 10s

commit-drive-scsi1: transferred 772.9 MiB of 962.3 GiB (0.08%) in 11s

commit-drive-scsi1: transferred 1.4 GiB of 962.3 GiB (0.15%) in 12s

commit-drive-scsi1: transferred 2.1 GiB of 962.3 GiB (0.22%) in 13s

.....

.....

commit-drive-scsi1: transferred 845.9 GiB of 962.3 GiB (87.90%) in 20m 11s

commit-drive-scsi1: transferred 846.6 GiB of 962.3 GiB (87.98%) in 20m 12s

commit-drive-scsi1: transferred 847.3 GiB of 962.3 GiB (88.05%) in 20m 13s

commit-drive-scsi1: Cancelling block job

commit-drive-scsi1: Done.

TASK ERROR: Failed to complete block commit: block job (commit) error: commit-drive-scsi1: 'commit' has been cancelled

qm config

qm config 2090
agent: 1
boot: order=scsi0;scsi1;ide2;net0
cores: 16
cpu: x86-64-v2-AES
description:
ide2: none,media=cdrom
memory: 98304
meta: creation-qemu=7.1.0,ctime=1692033904
name: GitFlex
net0: virtio=00:50:56:b5:29:2a,bridge=vmbr206,firewall=1
numa: 0
ostype: l26
parent: upd
scsi0: Barracuda-VM002p:vm-2090-disk-1.qcow2,aio=native,size=700G
scsi1: Barracuda-VM002p:vm-2090-disk-0.qcow2,aio=native,backup=0,size=1020G
scsihw: virtio-scsi-single
smbios1: uuid=6094ab64-3772-4ee2-957b-bdb26cf66898
sockets: 1
tags: dit
vmgenid: 264df2cf-898c-418a-9c76-672536856b95

log

pvedaemon[3610003]: VM 2090 qmp command failed - VM 2090 qmp command 'block-job-cancel' failed - Block job 'commit-drive-scsi1' not found

 

[Saron]

Just to make sure you didnt cancel the block job yourself? Do you see any additional information in the journal?

 

[Kosh]

I couldn't delete it even with the VM turned off.
I had to clone it and delete the original.

vm-2090-disk-0.qcow2: deleting snapshot 'upd' by commiting snapshot 'current'
running 'qemu-img commit /dev/Barracuda-VM002p/vm-2090-disk-0.qcow2'
qemu-img: Block job failed: No space left on device
The state of upd is now invalid. Don't try to clone or rollback it. You can only try to delete it again later
TASK ERROR: error commiting current to upd; command '/usr/bin/qemu-img commit /dev/Barracuda-VM002p/vm-2090-disk-0.qcow2' failed: exit code 1

there was plenty of space

 

[fiona]

Hi,
did you resize the image after the snapshot was taken? If, yes it might be https://bugzilla.proxmox.com/show_bug.cgi?id=7094

Please share the output of

qemu-img info --output=json --backing-chain /dev/Barracuda-VM002p/vm-2090-disk-0.qcow2
cat /etc/pve/qemu-server/2090.conf
pveversion -v

Make sure that the LV is active for the first command.

 

[Kosh]

Hi,
did you resize the image after the snapshot was taken? If, yes it might be https://bugzilla.proxmox.com/show_bug.cgi?id=7094

Please share the output of

qemu-img info --output=json --backing-chain /dev/Barracuda-VM002p/vm-2090-disk-0.qcow2
cat /etc/pve/qemu-server/2090.conf
pveversion -v

Make sure that the LV is active for the first command.

Thanks for the info, the old VM has already been deleted.
And yes, we expanded the VM's disk after the snapshot was taken.