Hardware: zyxel NAS server NSA325-v2,ARM arch, 2-bay dysk, the newest debian, the newest available kernel, the newest available lvm2 packages. root@debian:~# /sbin/vgchange -aly --ignorelockingfailure eld4 ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock failed: Cannot allocate memory 4 logical volume(s) in volume group "eld4" now active ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock failed: Cannot allocate memory the same problems when I create volume root@debian:~# uname -a Linux debian 3.13.1-kirkwood-tld-2 #1 PREEMPT Tue Feb 4 03:19:07 PST 2014 armv5tel GNU/Linux ii lvm2 2.02.95-8 armel Linux Logical Volume Manager Sounds similar to: https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-November/000391.html this is bug of kernel or LVM2 ?
hmmm.... root@debian:~# cat /etc/apt/sources.list deb http://ftp.us.debian.org/debian wheezy main deb http://security.debian.org/ wheezy/updates main contrib non-free root@debian:~# cat /etc/debian_version 7.3
after some use of disk, in dmesg I saw: [70518.895380] JBD2: Spotted dirty metadata buffer (dev = dm-2, blocknr = 7663232). There's a risk of filesystem corruption in case of system crash. [76948.242699] JBD2: Spotted dirty metadata buffer (dev = dm-2, blocknr = 84693853). There's a risk of filesystem corruption in case of system crash.
I'd like to confirm ... that version: 2.02.104-2 of lvm2 package is not affected. So this only needs to build newer version for wheezy distro (armel).
The userspace patch should be sufficient.