stop vm backup - vmlock was not removed

[informant]

Hi, if i stop a "hanging" backup with STOP, backup stopped, but vmlock was not removed automatical. i must do it manually. it´s a bug?

regards

 

[dietmar]

You tested with latest version (I thought this was fixed)?

 

[informant]

At the moment i use:
pveversion -v
proxmox-ve-2.6.32: 3.3-147 (running kernel: 2.6.32-34-pve)
pve-manager: 3.3-20 (running version: 3.3-20/d0640ef1)
pve-kernel-2.6.32-32-pve: 2.6.32-136
pve-kernel-2.6.32-33-pve: 2.6.32-138
pve-kernel-2.6.32-28-pve: 2.6.32-124
pve-kernel-2.6.32-30-pve: 2.6.32-130
pve-kernel-2.6.32-37-pve: 2.6.32-147
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-2.6.32-34-pve: 2.6.32-140
pve-kernel-2.6.32-31-pve: 2.6.32-132
lvm2: 2.02.98-pve4
clvm: 2.02.98-pve4
corosync-pve: 1.4.7-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.10-2
pve-cluster: 3.0-16
qemu-server: 3.3-20
pve-firmware: 1.1-3
libpve-common-perl: 3.0-24
libpve-access-control: 3.0-16
libpve-storage-perl: 3.0-30
pve-libspice-server1: 0.12.4-3
vncterm: 1.1-8
vzctl: 4.0-1pve6
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 2.1-12
ksm-control-daemon: 1.1-1
glusterfs-client: 3.5.2-1

i would update today to lastest version and would check in next time, if error comes back!

 

[longhair]

...

 

[informant]

@longhair,

this command is right and is not the issue of this thread.
issue is: on stop a backup, the command was not automatical exec after stopping command of the backup. read next time correct, pls! thanks

 

[wolfgang]

Hi, if i stop a "hanging" backup with STOP, backup stopped, but vmlock was not removed automatical. i must do it manually. it´s a bug?

regards

can you specify hanging?

is this reproducible?