Your message dated Tue, 19 Aug 2014 11:54:51 +0000
with message-id <20140819115451.ga14...@shell.waldi.eu.org>
and subject line fixed
has caused the Debian Bug report #740456,
regarding LVM operations returns: [vectors]: munlock failed: Cannot allocate
memory
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
740456: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=740456
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: lvm2
Version: 2.02.95-8
Severity: critical
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:~# lvcreate -v -L 10G eld4 -n EL0x
Setting logging type to disk
Finding volume group "eld4"
Archiving volume group "eld4" metadata (seqno 15).
Creating logical volume EL0x
Creating volume group backup "/etc/lvm/backup/eld4" (seqno 16).
Found volume group "eld4"
activation/volume_list configuration setting not defined: Checking
only host tags for eld4/EL0x
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: mlock
failed: Cannot allocate memory
Creating eld4-EL0x
Loading eld4-EL0x table (253:4)
Resuming eld4-EL0x (253:4)
ffff0000-ffff1000 r-xp 00000000 00:00 0 [vectors]: munlock
failed: Cannot allocate memory
Clearing start of logical volume "EL0x"
Creating volume group backup "/etc/lvm/backup/eld4" (seqno 16).
Logical volume "EL0x" created
root@debian:~# lvs | grep EL0x
EL0x eld4 -wi-a--- 10.00g
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
Should I use this volume or it is corrupted ?
I submitted that before, here:
https://bugzilla.kernel.org/show_bug.cgi?id=71361
...but I think now that this is debian problem, not kernel....?
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
-- System Information:
Debian Release: 7.3
APT prefers stable
APT policy: (500, 'stable')
Architecture: armel (armv5tel)
Kernel: Linux 3.13.1-kirkwood-tld-2 (PREEMPT)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash
Versions of packages lvm2 depends on:
ii dmsetup 2:1.02.74-8
ii initscripts 2.88dsf-41+deb7u1
ii libc6 2.13-38
ii libdevmapper-event1.02.1 2:1.02.74-8
ii libdevmapper1.02.1 2:1.02.74-8
ii libgcc1 1:4.7.2-5
ii libreadline5 5.2+dfsg-2~deb7u1
ii libudev0 175-7.2
ii lsb-base 4.1+Debian8+deb7u1
lvm2 recommends no packages.
lvm2 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 2.02.104-1
This is fixed in the specified version. For an upgrade to stable,
please show that this problem actually breaks things.
Bastian
--
--- End Message ---
