Debian Bug report logs - #740456
LVM operations returns: [vectors]: munlock failed: Cannot allocate memory

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Marcin T <marcint43@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>, Marcin T <marcint43@gmail.com>

Subject: LVM operations returns: [vectors]: munlock failed: Cannot allocate memory

Date: Sat, 1 Mar 2014 21:06:55 +0100

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

Message #10 received at 740456@bugs.debian.org (full text, mbox, reply):

From: Marcin T <marcint43@gmail.com>

To: 740456@bugs.debian.org

Subject: probably fixed in 2.02.99

Date: Mon, 3 Mar 2014 00:07:55 +0100

> Skip mlocking [vectors] on arm architecture.

could you release new version to wheezy ?

Message #15 received at 740456@bugs.debian.org (full text, mbox, reply):

From: Marcin T <marcint43@gmail.com>

To: 740456@bugs.debian.org

Subject: Re: probably fixed in 2.02.99

Date: Mon, 3 Mar 2014 22:59:17 +0100

I'd like to confirm.
2.02.104-2 does not have this bug.



2014-03-03 0:07 GMT+01:00 Marcin T <marcint43@gmail.com>:
>> Skip mlocking [vectors] on arm architecture.
>
> could you release new version to wheezy ?

Message #20 received at 740456@bugs.debian.org (full text, mbox, reply):

From: jeanmarc.lacroix@free.fr

To: jeanmarc.lacroix@free.fr, 740456@bugs.debian.org

Subject: [vectors]: munlock failed: Cannot allocate memory, confirmation on Wheezy 7.5 ARM

Date: Tue, 17 Jun 2014 06:47:14 +0200 (CEST)

Hi,

I confirm this problem on Cubieboard 1 (SocA10) with Debian Wheezy 7.5 and kernel


root@cubie:/etc# lvcreate --verbose --size 200M --name lv_tmp vg_system
    Setting logging type to disk
    Finding volume group "vg_system"
  Logical volume "lv_tmp" already exists in volume group "vg_system"
root@cubie:/etc# lvremove --verbose /dev/mapper/vg_system-lv_tmp
    Using logical volume(s) on command line
Do you really want to remove active logical volume lv_tmp? [y/n]: y
    Archiving volume group "vg_system" metadata (seqno 4).
    Found volume group "vg_system"
  ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: mlock failed: Cannot allocate memory
    Removing vg_system-lv_tmp (254:0)
    Releasing logical volume "lv_tmp"
  ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: munlock failed: Cannot allocate memory
    Creating volume group backup "/etc/lvm/backup/vg_system" (seqno 5).
  Logical volume "lv_tmp" successfully removed

root@cubie:/etc# uname -a
Linux cubie 3.4.91 #4 PREEMPT Mon Jun 16 18:30:37 CEST 2014 armv7l GNU/Linux

In order to test, i have installed on my Wheezy (7.5) the new jessie lvm2 package so that ....

root@cubie:/etc# apt-get install -t jessie lvm2
Reading package lists... Done
Building dependency tree      
Reading state information... Done
The following package was automatically installed and is no longer required:
  libffi5
Use 'apt-get autoremove' to remove it.
The following extra packages will be installed:
  dmsetup libc6 libdevmapper1.02.1 libffi6 libp11-kit0 locales
Suggested packages:
  glibc-doc thin-provisioning-tools
The following NEW packages will be installed:
  libffi6
The following packages will be upgraded:
  dmsetup libc6 libdevmapper1.02.1 libp11-kit0 locales lvm2
6 upgraded, 1 newly installed, 0 to remove and 166 not upgraded.
Need to get 8898 kB of archives.
After this operation, 1603 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get:1 http://ftp.fr.debian.org/debian/ jessie/main libffi6 armhf 3.1-2 [18.1 kB]
Get:2 http://ftp.fr.debian.org/debian/ jessie/main libp11-kit0 armhf 0.20.2-5 [67.2 kB]
Get:3 http://ftp.fr.debian.org/debian/ jessie/main locales all 2.19-1 [3926 kB]
Package configuration

Please note that glibc is also updated, but i dont update my kernel.

In order to do that, my sources.list is :

root@cubie:/etc# cat /etc/apt/sources.list

deb     http://ftp.fr.debian.org/debian/ wheezy main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ wheezy main contrib non-free

deb     http://security.debian.org/ wheezy/updates main contrib non-free
deb-src http://security.debian.org/ wheezy/updates main contrib non-free

deb     http://ftp.debian.org/debian/ wheezy-backports main contrib non-free

deb     http://www.emdebian.org/debian/ wheezy main

deb     http://ftp.fr.debian.org/debian/ jessie main contrib non-free
deb-src http://ftp.fr.debian.org/debian/ jessie main contrib non-free

....and preferences are ....

root@cubie:/etc# cat /etc/apt/preferences
# file /etc/apt/preferences

Package: *
Pin: release a=wheezy-backports
Pin-Priority: 920

Package: *
Pin: release a=wheezy
Pin-Priority: 910

Package: *
Pin: release a=apt-build
Pin-Priority: 900

Package: *
Pin: release a=jessie
Pin-Priority: 890

Package: *
Pin: release a=testing
Pin-Priority: 80

Package: *
Pin: release a=unstable
Pin-Priority: 33


After installation, the system is stable

root@cubie:/etc# dpkg -l |grep -v ii
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                            Version                   Architecture Description
+++-===============================-=========================-============-========================================================================

and following command is now ok

root@cubie:/etc#  lvcreate --verbose --size 200M --name lv_tmp vg_system
    Setting logging type to disk
    Finding volume group "vg_system"
    Archiving volume group "vg_system" metadata (seqno 5).
    Creating logical volume lv_tmp
    Creating volume group backup "/etc/lvm/backup/vg_system" (seqno 6).
    Activating logical volume "lv_tmp".
    activation/volume_list configuration setting not defined: Checking only host tags for vg_system/lv_tmp
    Creating vg_system-lv_tmp
    Loading vg_system-lv_tmp table (254:0)
    Resuming vg_system-lv_tmp (254:0)
    Wiping known signatures on logical volume "vg_system/lv_tmp"
    Initializing 4.00 KiB of logical volume "vg_system/lv_tmp" with value 0.
    Creating volume group backup "/etc/lvm/backup/vg_system" (seqno 6).
  Logical volume "lv_tmp" created

and ....

root@cubie:/etc# lvremove --verbose /dev/mapper/vg_system-lv_tmp 
    Using logical volume(s) on command line
Do you really want to remove active logical volume lv_tmp? [y/n]: y
    Archiving volume group "vg_system" metadata (seqno 6).
    Removing vg_system-lv_tmp (254:0)
    Releasing logical volume "lv_tmp"
    Creating volume group backup "/etc/lvm/backup/vg_system" (seqno 7).
  Logical volume "lv_tmp" successfully removed


The biggest problem is to know or not if this error can corrupt or not file system ?
Please can you update lvm2 package ?
Many thanks in advance

-- 
-- 
--------------------------------------
  -- Jean-Marc LACROIX                 --
   -- mailto : jeanmarc.lacroix@free.fr --
     ---------------------------------------

Message #25 received at 740456-done@bugs.debian.org (full text, mbox, reply):

From: Bastian Blank <waldi@debian.org>

To: 740456-done@bugs.debian.org

Subject: fixed

Date: Tue, 19 Aug 2014 11:54:51 +0000

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

-- 

Send a report that this bug log contains spam.