[PVE-User] Backup locked vm forever

Dariusz Bączkowski dariusz.baczkowski at esyscoder.pl
Tue Jun 18 13:06:18 CEST 2013


Dnia wtorek, 18 czerwca 2013 o 12:40:25 Dariusz Bączkowski napisał(a):
> Hi,
> 
> Backup stopped working on 2 nodes in my cluster. I cannot kill -9 below
> processes and do not find any solution on forum. How can I make backup work
> again? I would like a solution without resetting nodes.

Found solution:
http://forum.proxmox.com/threads/9099-vm-locked-after-failed-backup-can-t-
unlock?p=72449#post72449

Doing this on one node unlocked vms on both nodes.

> 
> root at pvec1b:/var/lock/qemu-server# ps aux |grep -- --lock
> root         964  0.0  0.2 181648 37036 ?        D    11:55   0:00
> /usr/bin/perl -w /usr/sbin/qm set 410 --lock backup
> root        5135  0.0  0.0   7812   880 pts/7    S+   12:31   0:00 grep --
> -- lock
> root      859424  0.0  0.2 181648 37036 ?        D    Jun17   0:00
> /usr/bin/perl -w /usr/sbin/qm set 401 --lock backup
> root      920036  0.0  0.2 181648 37040 ?        D    Jun17   0:00
> /usr/bin/perl -w /usr/sbin/qm set 405 --lock backup
> root     1019930  0.0  0.2 181648 37036 ?        D    07:30   0:00
> /usr/bin/perl -w /usr/sbin/qm set 406 --lock backup
> 
> root at pvec1b:/var/lock/qemu-server# lsof /var/lock/qemu-server/*
> COMMAND     PID USER   FD   TYPE DEVICE SIZE/OFF  NODE NAME
> qm          964 root    6wW  REG    9,2        0 26856 /var/lock/qemu-
> server/lock-410.conf
> qm       859424 root    6wW  REG    9,2        0 24939 /var/lock/qemu-
> server/lock-401.conf
> qm       920036 root    6wW  REG    9,2        0 24621 /var/lock/qemu-
> server/lock-405.conf
> qm      1019930 root    6wW  REG    9,2        0 26809 /var/lock/qemu-
> server/lock-406.conf
> 
> qm unlock 401
> trying to aquire lock...can't lock file
> '/var/lock/qemu-server/lock-401.conf' - got timeout
> 
> root at pvec1b:/var/lock/qemu-server# pvecm status
> Version: 6.2.0
> Config Version: 3
> Cluster Name: pvec1
> Cluster Id: 3387
> Cluster Member: Yes
> Cluster Generation: 352
> Membership state: Cluster-Member
> Nodes: 3
> Expected votes: 3
> Total votes: 3
> Node votes: 1
> Quorum: 2
> Active subsystems: 5
> Flags:
> Ports Bound: 0
> Node name: pvec1b
> Node ID: 2
> Multicast addresses: 239.192.13.72
> Node addresses: 10.71.2.1
> root at pvec1b:/var/lock/qemu-server# pvecm nodes
> Node  Sts   Inc   Joined               Name
>    1   M    352   2013-06-16 16:01:03  pvec1a
>    2   M     88   2013-03-22 15:42:37  pvec1b
>    3   M    232   2013-04-22 18:19:54  pvec1c
> 
> pveversion -v
> pve-manager: 2.3-13 (pve-manager/2.3/7946f1f1)
> running kernel: 2.6.32-19-pve
> proxmox-ve-2.6.32: 2.3-93
> pve-kernel-2.6.32-19-pve: 2.6.32-93
> lvm2: 2.02.95-1pve2
> clvm: 2.02.95-1pve2
> corosync-pve: 1.4.4-4
> openais-pve: 1.1.4-2
> libqb: 0.10.1-2
> redhat-cluster-pve: 3.1.93-2
> resource-agents-pve: 3.9.2-3
> fence-agents-pve: 3.1.9-1
> pve-cluster: 1.0-36
> qemu-server: 2.3-18
> pve-firmware: 1.0-21
> libpve-common-perl: 1.0-49
> libpve-access-control: 1.0-26
> libpve-storage-perl: 2.3-6
> vncterm: 1.0-3
> vzctl: 4.0-1pve2
> vzprocps: 2.0.11-2
> vzquota: 3.1-1
> pve-qemu-kvm: 1.4-8
> ksm-control-daemon: 1.1-1

-- 
Pozdrawiam,
Dariusz Bączkowski

ESYSCODER Dariusz Bączkowski
e-mail: biuro at esyscoder.pl
tel.: +48 720 820 220
fax: +48 947 166 554
http://esyscoder.pl/
http://system-taxi.pl/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 230 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.proxmox.com/pipermail/pve-user/attachments/20130618/b4fe765b/attachment.sig>


More information about the pve-user mailing list