vzdump on CentOS 5.6 (x64) with internal error (maps lock < unlock)

H

hk@

Renowned Member
Feb 10, 2010
248
8
83
Vienna
kapper.net
Hi
as I found no better place to discuss this I try this one - please redirect me to the proper place if I missed it in my search.

First I had to do some tricks to get it installed:
perl-LockFile-Simple and cstream need to get installed (typically from dag.wieers.com repos).
Then the vzdump-1.2-6 rpm could get installd and after that I had to:
ln -s /usr/share/perl5/PVE /usr/lib64/perl5/site_perl/5.8.8/x86_64-linux-thread-multi/PVE

(Thanks go to Chris Schuld http://chrisschuld.com/2009/11/installing-vzdump-for-openvz-on-centos/ )

Now everything seems fine, but I get a strange internal error in the log and can't figure out why - any advise would be greatly appreciated.

Code: 
212: Jun 19 05:57:57 INFO: Starting Backup of VM 212 (openvz)
212: Jun 19 05:57:57 INFO: CTID 212 exist mounted running
212: Jun 19 05:57:57 INFO: status = CTID 212 exist mounted running
212: Jun 19 05:57:57 INFO: backup mode: snapshot
212: Jun 19 05:57:57 INFO: bandwidth limit: 10240 KB/s
212: Jun 19 05:57:57 INFO: creating lvm snapshot of /dev/mapper/store-vz ('/dev/store/vzsnap-k77-0')
[COLOR=#ff0000]212: Jun 19 05:57:58 INFO:   Internal error: Maps lock 14467072 < unlock 14741504[/COLOR]
212: Jun 19 05:57:58 INFO:   Logical volume "vzsnap-k77-0" created
212: Jun 19 05:57:58 INFO: creating archive '/vz/dump/vzdump-openvz-212-2011_06_19-05_57_57.tgz'
212: Jun 19 08:23:28 INFO: Total bytes written: 60063662080 (56GiB, 6.6MiB/s)
212: Jun 19 08:23:28 INFO: archive file size: 44.04GB
212: Jun 19 08:23:28 INFO: delete old backup '/vz/dump/vzdump-openvz-212-2011_06_13-18_26_52.tgz'
[COLOR=#ff0000]212: Jun 19 08:24:27 INFO:   Internal error: Maps lock 14475264 < unlock 14749696[/COLOR]
212: Jun 19 08:24:28 INFO:   Logical volume "vzsnap-k77-0" successfully removed
212: Jun 19 08:24:28 INFO: Finished Backup of VM 212 (02:26:31)
 
Dear Dietmar,
thanks for the pointer - I have to investigate this further I think, as Redhat EL5 / CentOS 5 is running a much older kernel than mentioned in this link I can not make sense yet, but then it might also relate to backports done to either the kernel or the lvm tools.
Anyways, it is comforting that this seems to be a "no problem" internal error :)

My last question would be: Is there a "right" place to look for a current vzdump in RPM or SRPM packaging? The one on at http://download.openvz.org/contrib/utils/vzdump/ doesn't seem to be a recent release/update.

Thank you in advance
hk
 
You must log in or register to reply here.
Top Bottom