Debian Bug report logs - #581593
udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Toggle useless messages

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

From: QuadCEM <quadcem@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Thu, 13 May 2010 23:03:07 -0500

Package: udev
Version: 154-1
Severity: important
Tags: sid

During boot, a bunch of ominous warnings come up along the lines of:

kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree, please use
SYMLINK+= or change the kernel to provide the proper name

All of my partitions except boot are encrypted.  The system seems to boot like
normal otherwise, as far as I can tell so far.

# dpkg -l
ii  libgudev-1.0-0                                           154-1
GObject-based wrapper library for libudev
ii  libudev0                                                 154-1
libudev shared library
ii  udev                                                     154-1
/dev/ and hotplug management daemon




-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (900, 'unstable'), (800, 'testing'), (700, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-xen-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages udev depends on:
ii  debconf [debconf-2.0]        1.5.32      Debian configuration management sy
ii  libc6                        2.10.2-8    Embedded GNU C Library: Shared lib
ii  libselinux1                  2.0.94-1    SELinux runtime shared libraries
ii  libusb-0.1-4                 2:0.1.12-14 userspace USB programming library
ii  lsb-base                     3.2-23.1    Linux Standard Base 3.2 init scrip
ii  util-linux                   2.16.2-0    Miscellaneous system utilities

Versions of packages udev recommends:
ii  pciutils                      1:3.1.7-3  Linux PCI Utilities
ii  usbutils                      0.87-1     Linux USB utilities

udev suggests no packages.

-- debconf information:
  udev/new_kernel_needed: false
  udev/title/upgrade:
  udev/reboot_needed:

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

From: md@Linux.IT (Marco d'Itri)

To: QuadCEM <quadcem@gmail.com>, 581593@bugs.debian.org

Cc: control@bugs.debian.org, lvm2@packages.debian.org

Subject: Re: Bug#581593: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Fri, 14 May 2010 08:24:48 +0200

[Message part 1 (text/plain, inline)]

reassign 581593 dmsetup
thanks

On May 14, QuadCEM <quadcem@gmail.com> wrote:

> During boot, a bunch of ominous warnings come up along the lines of:
> 
> kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree, please use
> SYMLINK+= or change the kernel to provide the proper name
So you conclude that this is a udev bug?

-- 
ciao,
Marco

[signature.asc (application/pgp-signature, inline)]

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

From: QuadCEM <quadcem@gmail.com>

To: Marco d'Itri <md@Linux.IT>

Cc: 581593@bugs.debian.org

Subject: Re: Bug#581593: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Fri, 14 May 2010 03:03:05 -0500

It might be related to dmsetup ... I assumed it was udev because the 
warnings started appearing right after I upgraded udev to 154-1.  Plus, 
the full warning said:

udevd-work[180]: kernel-provided name 'dm-0' and 
NAME='/mapper/sdb2_crypt' disagree, please use SYMLINK+= or change the 
kernel to provide the proper name


On 05/14/2010 01:24 AM, Marco d'Itri wrote:
> reassign 581593 dmsetup
> thanks
>
> On May 14, QuadCEM<quadcem@gmail.com>  wrote:
>
>> During boot, a bunch of ominous warnings come up along the lines of:
>>
>> kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree, please use
>> SYMLINK+= or change the kernel to provide the proper name
> So you conclude that this is a udev bug?
>

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

From: Peter Rajnoha <prajnoha@redhat.com>

To: QuadCEM <quadcem@gmail.com>, 581593@bugs.debian.org

Subject: Re: Bug#581593: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Fri, 14 May 2010 10:26:58 +0200

On 05/14/2010 10:03 AM, QuadCEM wrote:
> It might be related to dmsetup ... I assumed it was udev because the
> warnings started appearing right after I upgraded udev to 154-1.  Plus,
> the full warning said:
> 
> udevd-work[180]: kernel-provided name 'dm-0' and
> NAME='/mapper/sdb2_crypt' disagree, please use SYMLINK+= or change the
> kernel to provide the proper name
> 

Udev 154 includes a few changes for "NAME" rule handling.

[ANNOUNCE] udev 154 release:

"Udev now gradually starts to pass control over the primary device nodes
and their names to the kernel, and will in the end only manage the
permissions of the node, and possibly create additional symlinks.
As a first step NAME="" will be ignored, and NAME= settings with names
other than the kernel provided name will result in a logged warning..."

Debian version of device-mapper rules use the NAME="mapper/$env{DM_NAME}",
it should be SYMLINK="mapper/$env{DM_NAME}".

Also, the NAME="" that was supposed to suppress node creation on ADD event
is ignored since now as well (unfortunately, this was the only way to do
that suppression somehow). We (upstream dm/lvm2) are still trying to discuss
this issue with upstream udev developers...

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

From: Sheridan Hutchinson <sheridan@shezza.org>

To: Peter Rajnoha <prajnoha@redhat.com>

Cc: 581593@bugs.debian.org

Subject: Re: Bug#581593: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Sat, 15 May 2010 11:35:22 +0100

In the interim is there any known work-around for this?

It's a bit of a jip because my / file system initially mounts as read only.

I guess I'll just roll udev back to the previous version and rebuild
the kernel against that then unless anyone has any other advice?

-- 
Regards,
Sheridan Hutchinson
sheridan@shezza.org

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

From: Jean-Luc Coulon <jean-luc@famille-coulon.fr>

To: 581593@bugs.debian.org

Subject: Not to be assigned to dm-setup

Date: Sat, 15 May 2010 21:50:11 +0200

Hi,

I think reastsignated it to dmsetup was not a good idea.
I've a machine without encryptted filesystem (and without dmsetup
installed) and I've also this message.
This time, it is against 'input/uinput':

Sat May 15 21:40:47 2010: udevd-work[406]: kernel-provided name 'uinput'
and NAME= 'input/uinput' disagree, please use SYMLINK+= or change the
kernel to provide the proper name

Regards

Jean-Luc

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

From: Sheridan Hutchinson <sheridan@shezza.org>

To: Jean-Luc Coulon <jean-luc@famille-coulon.fr>

Cc: 581593 <581593@bugs.debian.org>

Subject: +

Date: Sat, 15 May 2010 23:47:45 +0100

I also found this apparently related bug, which has been reassigned
back to udev:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581715

-- 
Regards,
Sheridan Hutchinson
sheridan@shezza.org

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

From: Peter Rajnoha <prajnoha@redhat.com>

To: Sheridan Hutchinson <sheridan@shezza.org>

Cc: 581593@bugs.debian.org

Subject: Re: Bug#581593: udev: kernel-provided name 'dm-0' and NAME='/mapper/sdb2_crypt' disagree

Date: Mon, 17 May 2010 13:51:15 +0200

On 05/15/2010 12:35 PM, Sheridan Hutchinson wrote:
> In the interim is there any known work-around for this?
> 
> It's a bit of a jip because my / file system initially mounts as read only.
> 

Well, it should be just a warning, it shouldn't break anything.
As for the warning message removal, the only right way is to
create nodes as /dev/dm-X and then symlinks in /dev/mapper,
so changing that one line in the 55-dm.rules:

  ENV{DM_NAME}=="?*", NAME="mapper/$env{DM_NAME}", SYMLINK+="$kernel"

and use this instead:

  ENV{DM_NAME}=="?*", SYMLINK+="mapper/$env{DM_NAME}"

(this is what we had to agree on with udev team once)

As for the suppression of the ADD event, we don't have a clear
solution for this yet, discussions still ongoing. The problem is that
device-mapper devices should be visible under /dev only when the
table is loaded and made live - and that's on CHANGE event
(the ADD event is generated automatically outside of device-mapper
in kernel, we're not in control of this event at all).

On the other hand, we have "udevadm trigger --action=add" used
mostly at boot. That's the "ACTION=="add", ENV{STARTUP}!="1"..."
rule that's in 55-dm.rules as well that tried to provide a way
to use this trigger for dm devices when needed (but still, it required
the "STARTUP" variable to be set).

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

From: Sheridan Hutchinson <sheridan@shezza.org>

To: 581593 <581593@bugs.debian.org>

Cc: Peter Rajnoha <prajnoha@redhat.com>

Subject: Update

Date: Mon, 17 May 2010 19:26:13 +0100

Yep, what you've described is completely accurate; the message is
harmless and doesn't interfer with normal operations.

There was a small (and totally unrelated) bug in the init-scripts
package which has now been fixed that caused my problem.

-- 
Regards,
Sheridan Hutchinson
sheridan@shezza.org

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

From: Jeremie Le Hen <jeremie@le-hen.org>

To: Sheridan Hutchinson <sheridan@shezza.org>

Cc: 581593 <581593@bugs.debian.org>, Peter Rajnoha <prajnoha@redhat.com>

Subject: Re: Update

Date: Wed, 19 May 2010 13:53:34 +0200

Hi Sheridan,

On Mon, May 17, 2010 at 07:26:13PM +0100, Sheridan Hutchinson wrote:
> Yep, what you've described is completely accurate; the message is
> harmless and doesn't interfer with normal operations.
> 
> There was a small (and totally unrelated) bug in the init-scripts
> package which has now been fixed that caused my problem.

I've had a similar warning message when trying to decrypt my encrypted
root filesystem, except that NAME is not "mapper/sdb2_crypt" but
something like "mapper/temporary-cryptsetup".

I've modified my 55-dm.rules in my kernel initrd, the warning message
has gone away but I'm still getting the following error:
    cryptsetup: cryptsetup filed, bad password or options?

I've tried to run udevd with --debug, but it issues way too much logs on
my console to be analyzed and I don't think I can capture the output in
a file as it's occuring at the initrd stage.

Thanks.
Best regards,
-- 
Jeremie Le Hen

Humans are born free and equal.  But some are more equal than others.
					    Coluche

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

From: Bastian Blank <waldi@debian.org>

To: 578826-done@bugs.debian.org

Subject: fixed

Date: Sat, 6 Sep 2014 20:11:30 +0200

The udev rules do not longer rename devices.

Bastian

-- 
There is an order of things in this universe.
		-- Apollo, "Who Mourns for Adonais?" stardate 3468.1

Send a report that this bug log contains spam.