[Bug 797226] Re: /dev/dm-10 is not created for LVM volume

Bug Watch Updater 797226 at bugs.launchpad.net
Fri Oct 27 16:32:00 UTC 2017


Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=690308.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2011-03-23T20:40:12+00:00 G. wrote:

I think I've found why none of my lvm mounts are working on boot up.

First the vgchange in fedora-storage-init never seems to get hit.   And
udev seems to have a problem setting up the drivers as well.

[root at liandra systemd]# /sbin/lvm vgchange -a y --sysinit
  10 logical volume(s) in volume group "LiandraStore" now active
  semid 32768: semop failed for cookie 0xd4d83af: incorrect semaphore state
  Failed to set a proper state for notification semaphore identified by cookie value 223183791 (0xd4d83af) to initialize waiting for incoming notifications.
  /dev/mapper/LiandraStore-VirtualMachines not set up by udev: Falling back to direct node creation.
  /dev/mapper/LiandraStore-Old--Liandra not set up by udev: Falling back to direct node creation.
  /dev/mapper/LiandraStore-Backups not set up by udev: Falling back to direct node creation.
  /dev/mapper/LiandraStore-LiveCD not set up by udev: Falling back to direct node creation.
  /dev/mapper/LiandraStore-iTunes_Media not set up by udev: Falling back to direct node creation.
  /dev/mapper/LiandraStore-DVD--Working not set up by udev: Falling back to direct node creation.
  The link /dev/LiandraStore/VirtualMachines should had been created by udev but it was not found. Falling back to direct link creation.
  The link /dev/LiandraStore/Old-Liandra should had been created by udev but it was not found. Falling back to direct link creation.
  The link /dev/LiandraStore/Backups should had been created by udev but it was not found. Falling back to direct link creation.
  The link /dev/LiandraStore/LiveCD should had been created by udev but it was not found. Falling back to direct link creation.
  The link /dev/LiandraStore/iTunes_Media should had been created by udev but it was not found. Falling back to direct link creation.
  The link /dev/LiandraStore/DVD-Working should had been created by udev but it was not found. Falling back to direct link creation.


Any ideas how I debug this further?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/0

------------------------------------------------------------------------
On 2011-03-23T20:41:52+00:00 G. wrote:

This may be related to by dbus not starting as well in bug: 689861.
Not sure.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/1

------------------------------------------------------------------------
On 2011-03-24T08:57:04+00:00 Harald wrote:

are you sure udevd is running?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/2

------------------------------------------------------------------------
On 2011-03-24T13:13:11+00:00 G. wrote:

I'm assuming it is:


[root at liandra ~]# ps -ef | grep udev
root       488     1  0 Mar23 ?        00:00:00 /sbin/udevd
root     18778 18319  0 09:12 pts/1    00:00:00 grep --color=auto udev

[root at liandra ~]# lvcreate -L 10G -n Test LiandraStore 
  /dev/mapper/LiandraStore-Test not set up by udev: Falling back to direct node creation.
  The link /dev/LiandraStore/Test should had been created by udev but it was not found. Falling back to direct link creation.
  Logical volume "Test" created

[root at liandra ~]# lvremove LiandraStore/Test
Do you really want to remove active logical volume Test? [y/n]: y
  Logical volume "Test" successfully removed
  semid 98304: semop failed for cookie 0xd4d613a: incorrect semaphore state
  Failed to set a proper state for notification semaphore identified by cookie value 223174970 (0xd4d613a) to initialize waiting for incoming notifications.


Any further tests I ran run to verify it is running correctly?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/3

------------------------------------------------------------------------
On 2011-03-24T13:44:12+00:00 Harald wrote:

any ideas from the lvm team, what's going wrong here?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/4

------------------------------------------------------------------------
On 2011-03-24T14:21:54+00:00 Milan wrote:

This usually means, that you are using udev-enabled lvm (default in
Fedora) but there are missing lvm udev rules (explicitly rule with
"dmsetup udevcomplete" call, 95-dm-notify.rules).

lvm will fallback to manual node removal (I think that the warning is
about semaphore state is some minor bug in lvm code but it is just
consequence - if udev rules missing, your system is simply
misconfigured.)

Verify, that device-mapper is properly installed.

To diagnose it, please run the lvm command with -vvvv and add output
here.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/5

------------------------------------------------------------------------
On 2011-03-29T13:23:30+00:00 G. wrote:

Created attachment 488442
Verbose lvcreate command

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/6

------------------------------------------------------------------------
On 2011-03-29T13:24:05+00:00 G. wrote:

Also verified the /lib/udev/rules.d/95-dm-notify.rules is the same in
F15 as it is in other releases.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/7

------------------------------------------------------------------------
On 2011-03-29T13:55:17+00:00 Peter wrote:

What's the kernel version used? Is this a stock Fedora kernel?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/8

------------------------------------------------------------------------
On 2011-03-29T13:58:25+00:00 G. wrote:

Yes it's stock.   2.6.38-1.fc15.x86_64

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/9

------------------------------------------------------------------------
On 2011-03-31T14:30:19+00:00 Peter wrote:

Well, based on the log, uevent was not generated correctly:

  " Uevent not generated! Calling udev_complete internally to avoid
process lock-up."

This decrements the value of the semaphore used for synchronization.
However, if the event (for some reason) *is* generated despite the fact
that the kernel function responsible for sending the uevent reports a
failure and then we decrement the value once again from within the udev
rules based on the generated event (/lib/udev/rules.d/95-dm-
notify.rules), we can end up with that:

  "semid 32768: semop failed for cookie 0xd4d83af: incorrect semaphore
state..."

The other messages about "... not set up by udev. Falling back to direct
node creation" is just a consequence of failed synchronisation with udev
(since we decremented semaphore value prematurely).

However I'm not quite sure now why this happens. It could be a bug in
kernel code as well... (but I can't reproduce that)

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/10

------------------------------------------------------------------------
On 2011-03-31T15:31:04+00:00 Harald wrote:

you might also try the new udev version in F15

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/11

------------------------------------------------------------------------
On 2011-04-11T15:05:54+00:00 G. wrote:

New version in F15 seems to have solved the problems.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/797226/comments/12


** Changed in: lvm2 (Fedora)
       Status: Unknown => Fix Released

** Changed in: lvm2 (Fedora)
   Importance: Unknown => High

-- 
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/797226

Title:
  /dev/dm-10 is not created for LVM volume

Status in lvm2 package in Ubuntu:
  Confirmed
Status in lvm2 package in Fedora:
  Fix Released

Bug description:
  Binary package hint: udev

  After I created 10th logical volume (shared - see below), udev did not create /dev/dm-10 device node:
  root at mf:~# ls -l /dev/mapper/
  total 0
  crw------- 1 root root 10, 236 2011-06-05 09:04 control
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-devs -> ../dm-3
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-devs2 -> ../dm-5
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-devs3 -> ../dm-6
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-devs4 -> ../dm-8
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-dspp -> ../dm-1
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-lxc -> ../dm-0
  lrwxrwxrwx 1 root root       7 2011-06-12 00:52 mf-mail -> ../dm-9
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-matchbox -> ../dm-4
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-muze -> ../dm-2
  lrwxrwxrwx 1 root root       8 2011-06-14 17:18 mf-shared -> ../dm-10
  lrwxrwxrwx 1 root root       7 2011-06-05 09:04 mf-tests -> ../dm-7
  root at mf:~# ls -l /dev/dm*
  brw-rw---- 1 root disk 251, 0 2011-06-05 09:04 /dev/dm-0
  brw-rw---- 1 root disk 251, 1 2011-06-05 09:04 /dev/dm-1
  brw-rw---- 1 root disk 251, 2 2011-06-05 09:04 /dev/dm-2
  brw-rw---- 1 root disk 251, 3 2011-06-05 09:04 /dev/dm-3
  brw-rw---- 1 root disk 251, 4 2011-06-05 09:04 /dev/dm-4
  brw-rw---- 1 root disk 251, 5 2011-06-05 09:04 /dev/dm-5
  brw-rw---- 1 root disk 251, 6 2011-06-05 09:04 /dev/dm-6
  brw-rw---- 1 root disk 251, 7 2011-06-05 09:04 /dev/dm-7
  brw-rw---- 1 root disk 251, 8 2011-06-05 09:04 /dev/dm-8
  brw-rw---- 1 root disk 251, 9 2011-06-12 00:52 /dev/dm-9
  root at mf:~#

  Ubuntu 11.04 server amd64, kernel 2.6.38-8-server.
  ii  udev                            167-0ubuntu3                       rule-based device node and kernel event manager
  ii  lvm2                            2.02.66-4ubuntu2                   The Linux Logical Volume Manager
  ii  libdevmapper-event1.02.1        2:1.02.48-4ubuntu2                 The Linux Kernel Device Mapper userspace library
  ii  libdevmapper1.02.1              2:1.02.48-4ubuntu2                 The Linux Kernel Device Mapper userspace library

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



More information about the foundations-bugs mailing list