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...
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
