incorrect sempahore state when removing logical volime

Bug #846061 reported by Ben Howard on 2011-09-09
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
Undecided
Unassigned

Bug Description

Error of " semid 294914: semop failed for cookie 0xd4d6f1d: incorrect semaphore state
  Failed to set a proper state for notification semaphore identified by cookie value 223178525 (0xd4d6f1d) to initialize waiting for incoming notifications." whilst removing logical volumes.

root@padfoot:/# lvscan
  ACTIVE '/dev/Padfoot/backup' [100.00 GiB] inherit
  ACTIVE '/dev/Padfoot/development' [100.00 GiB] inherit
  ACTIVE '/dev/Padfoot/images' [40.00 GiB] inherit
  ACTIVE '/dev/Padfoot/oneiric-chroot' [8.00 GiB] inherit
  ACTIVE '/dev/Padfoot/mirror' [79.83 GiB] inherit
root@padfoot:/media/Backup-500G# lvremove Padfoot/oneiric-chroot
Do you really want to remove active logical volume oneiric-chroot? [y/n]: y
  semid 294914: semop failed for cookie 0xd4d6f1d: incorrect semaphore state
  Failed to set a proper state for notification semaphore identified by cookie value 223178525 (0xd4d6f1d) to initialize waiting for incoming notifications.
  Logical volume "oneiric-chroot" successfully removed
root@padfoot:/# lvscan
  ACTIVE '/dev/Padfoot/backup' [100.00 GiB] inherit
  ACTIVE '/dev/Padfoot/development' [100.00 GiB] inherit
  ACTIVE '/dev/Padfoot/images' [40.00 GiB] inherit
  ACTIVE '/dev/Padfoot/mirror' [79.83 GiB] inherit

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: lvm2 2.02.66-4ubuntu3
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.22.1-0ubuntu2
Architecture: amd64
Date: Fri Sep 9 15:58:21 2011
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: lvm2
UpgradeStatus: No upgrade log present (probably fresh install)

Ben Howard (utlemming) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in lvm2 (Ubuntu):
status: New → Confirmed
Dan Kegel (dank) wrote :

Here's a handy script to reproduce the error. This uses dd to create an image file, so it doesn't require any real volumes.

And here's the key part of the log:

#libdm-deptree.c:865 Removing demo_vg-foo_lv (252:0)
#libdm-common.c:1153 Udev cookie 0xd4d4fb5 (semid 720897) created
#libdm-common.c:1166 Udev cookie 0xd4d4fb5 (semid 720897) incremented
#libdm-common.c:1054 Udev cookie 0xd4d4fb5 (semid 720897) incremented
#libdm-common.c:1226 Udev cookie 0xd4d4fb5 (semid 720897) assigned to dm_task type 2 with flags 0x0
#ioctl/libdm-iface.c:1821 dm remove (252:0) NF [16384]
#libdm-common.c:1081 Udev cookie 0xd4d4fb5 (semid 720897) decremented
#libdm-common.c:815 demo_vg-foo_lv: Stacking NODE_DEL (replaces other stacked ops)
#libdm-common.c:1069 semid 720897: semop failed for cookie 0xd4d4fb5: incorrect semaphore state
#libdm-common.c:1270 Failed to set a proper state for notification semaphore identified by cookie value 223170485 (0xd4d4fb5) to initialize waiting for incoming notifications.
#libdm-common.c:1096 Udev cookie 0xd4d4fb5 (semid 720897) destroyed

This is on Ubuntu 11.10. The warning does not occur on Ubuntu 11.04.

Dan Kegel (dank) wrote :
Dan Kegel (dank) wrote :
Dan Kegel (dank) wrote :
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers