[Bug 1256905] [NEW] lvcreate fails with 'mlock failed' on armhf

[Tim Connolly]

Public bug reported:

Ubuntu 13.04
Kernel version: 3.6.9
lvm2:
  Installed: 2.02.95-6ubuntu4
  Candidate: 2.02.95-6ubuntu4
  Version table:
 *** 2.02.95-6ubuntu4 0
        500 http://ports.ubuntu.com/ubuntu-ports/ raring/main armhf Packages
        100 /var/lib/dpkg/status

# lvcreate --name data --size 1024G vg0
  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
  /dev/vg0/data: not found: device not cleared
  Aborting. Failed to wipe start of new LV.
  ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: mlock failed: Cannot allocate memory
  device-mapper: remove ioctl on  failed: Device or resource busy
  ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: munlock failed: Cannot allocate memory
  semid 32768: semop failed for cookie 0xd4de1fe: incorrect semaphore state
  Failed to set a proper state for notification semaphore identified by cookie value 223207934 (0xd4de1fe) to initialize waiting for incoming notifications.

Possibly resolved with the application of this patch:
https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-November/000391.html

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: armhf raring

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1256905

Title:
  lvcreate fails with 'mlock failed' on armhf

Status in “lvm2” package in Ubuntu:
  New

Bug description:
  Ubuntu 13.04
  Kernel version: 3.6.9
  lvm2:
    Installed: 2.02.95-6ubuntu4
    Candidate: 2.02.95-6ubuntu4
    Version table:
   *** 2.02.95-6ubuntu4 0
          500 http://ports.ubuntu.com/ubuntu-ports/ raring/main armhf Packages
          100 /var/lib/dpkg/status

  # lvcreate --name data --size 1024G vg0
    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
    /dev/vg0/data: not found: device not cleared
    Aborting. Failed to wipe start of new LV.
    ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: mlock failed: Cannot allocate memory
    device-mapper: remove ioctl on  failed: Device or resource busy
    ffff0000-ffff1000 r-xp 00000000 00:00 0          [vectors]: munlock failed: Cannot allocate memory
    semid 32768: semop failed for cookie 0xd4de1fe: incorrect semaphore state
    Failed to set a proper state for notification semaphore identified by cookie value 223207934 (0xd4de1fe) to initialize waiting for incoming notifications.

  Possibly resolved with the application of this patch:
  https://lists.fedorahosted.org/pipermail/lvm2-commits/2012-November/000391.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1256905/+subscriptions