LVM - new kernel 3.6.11 - leaked on lvcreate invocation

[Petr Nosek]

The bug is described here (with photo): https://github.com/raspberrypi/linux/issues/185

I think, that solution is a new package of lvm2 - it's written here: http://readlist.com/lists/redhat.com/linux-lvm/1/6244.html

[Petr Nosek (petr-nosek)]

There is problem with LVM. The latest version works:
root@raspberrypi:/# uname -a
Linux raspberrypi 3.2.27+ #260 PREEMPT Thu Nov 8 00:34:12 GMT 2012 armv6l GNU/Linux

now I use this version:
root@raspberrypi:/var/log# uname -a
Linux raspberrypi 3.6.11+ #348 PREEMPT Tue Jan 1 16:33:22 GMT 2013 armv6l GNU/Linux

After reboot - these errors:

setting up lvm volume groups
mlock failed cannot allocate memory
munlock failed

After lvcreate:
root@raspberrypi:# lvcreate -L 1G -n test vg2t
File descriptor 8 (pipe:[15832]) leaked on lvcreate invocation. Parent PID 3635: bash
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory
Logical volume "test" created

some problems are described here: http://readlist.com/lists/redhat.com/linux-lvm/1/6244.html

[peter green (plugwash)]

Can you try to reproduce this with a debian armel or armhf system and if it's reproducable there report it to them.

Having a stable release whose lvm fails with a slightly newer kernel seems like a bad thing to me but I don't want to unilaterally move forward to a more recent lvm if I can help it.

[Petr Nosek (petr-nosek)]

I reported bug there: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=698153

Solution is patch in lvm2. Patch is there: https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-November/000391.html

Can you apply patch to lvm2 in raspbian and creating new package (due to aptitude safe-upgrade)?

[Petr Nosek (petr-nosek)]

Is it possible repair the bug? Solution has been posted.

[peter green (plugwash)]

I've just pushed version 2.02.95-4+rpi1 with that patch to the raspbian repository. Can you please test it and confirm whether it fixes your issue.

[Petr Nosek (petr-nosek)]

 Thank you. You can close this issue. Problem is resolved.