Lock what?

[SamTzu]

Can someone explain to me what just happened here?
There was no 130 on the host. What is that 103.lck?

host2:/backup# vzrestore vzdump-130.tgz 130
WARNING: waiting for /var/lib/vz/lock/103.lck lock since 16 seconds
WARNING: still waiting for /var/lib/vz/lock/103.lck lock after 38 seconds
WARNING: still waiting for /var/lib/vz/lock/103.lck lock after 60 seconds
can't lock VM 130
host2:/backup# vzrestore vzdump-130.tgz 133
INFO: restore openvz backup 'vzdump-130.tgz' using ID 133
INFO: extracting archive 'vzdump-130.tgz'
etc...

 

[dietmar]

WARNING: waiting for /var/lib/vz/lock/103.lck lock since 16 seconds

Another vzctl process accessing CT 103 is still running?

 

[SamTzu]

No 103 or 130 in the host. I had to vzrestore it as 133.
Thats what was so weird.

 

[dietmar]

No 103 or 130 in the host.

Oh, I can see that now - quite strange. Is that bug somehow reproducible?

 

[Robert_]

Hi there,

the solution is to create a folder called "lock" in /var/lib/vz/


edit: hmm mind you, afterwards when i try to run the vz i get the following output and the start fails

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:last sysfs file: /sys/kernel/uevent_seqnum

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:Oops: 0010 [#1] SMP

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:Call Trace:

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:Stack:

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:Code: Bad RIP value.

Message from syslogd@proxmox at Mar 20 13:17:24 ...
kernel:CR2: 0000000000000000

any idea what this is and how to fix?


kind regards,