Comment 9 for bug 458529

Revision history for this message
In , Zeuthen (zeuthen) wrote :

(In reply to comment #4)
> This is in fact just a corollary of dk-disks handling lvm/dm/md devices itself
> in the rules, instead of having dmsetup/mdadm etc. ship their own rules. These
> rules are currently being introduced upstream, but didn't trickle through all
> the distros yet.
>
> This was recently discussed at length in this Debian bug:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545032#56
>
> Upstream lvm2 fixed that a while ago in its udev rules:
> http://sourceware.org/ml/lvm2-cvs/2009-08/msg00018.html

Just FYI, the Fedora lvm2 packages omit these udev rules. It conflicted with dracut or anaconda or something so they decided to pull it. To add insult to injury, keep in mind that the Fedora lvm2 package maintainers practically are the upstream lvm2 maintainers. So they're not eating their own dog food. To say that I'm happy with the lvm2 maintainers would be a lie.

So I guess we have to ship our own crap in DKD for a while more.

>
> +ENV{DM_LV_NAME}=="?*_mlog", GOTO="lvm_end"
> +ENV{DM_LV_NAME}=="?*_mimage_[0-9]*", GOTO="lvm_end"
>