Bug#573073: regarding Bug#573073: delay at creating lvm devices

Milan Broz mbroz at redhat.com
Sun Sep 26 18:04:40 UTC 2010

On 09/26/2010 05:38 PM, Bastian Blank wrote:
> On Sun, Sep 26, 2010 at 11:22:32AM +0200, Milan Broz wrote:
>> With the upstream dm rules yo do not need special udev rules.
> Please provide a patch. The rules are RedHat specific (see the
> definition of DM_SBIN_PATH, which even is a workaround for dracut).

Thanks for answer, but I am not sure what you mean here.

dmsetup is in Debian in /sbin, this is upstream:

# Set proper sbin path, /sbin has higher priority than /usr/sbin.                                                                          
TEST!="$env{DM_SBIN_PATH}/dmsetup", ENV{DM_SBIN_PATH}="/usr/sbin"                                                                          
TEST!="$env{DM_SBIN_PATH}/dmsetup", GOTO="dm_end"                                                                                          

What is Red Hat specific here?

Maybe it can be generated during configure but it is really detail.

The important thing is that link and node creation is synchronised
with the upstream rules.

Please try to accept that udev implementation is compromise
between udev and lvm/device-mapper upstream.
(I understand some of your concerns and I am not fan of some
concepts too but it was decided to go his way - and it works
in other distros already.)

We cannot have part of device-mapper programs using udev
(like cryptsetup) and other ignore it.

I am using Debian unstable too and see several udev related
warnings (lvm over LUKS) during boot - clearly caused by not updated
Debian udev dm rules.


More information about the pkg-lvm-maintainers mailing list