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 +ENV{DM_LV_NAME}=="?*_mlog", GOTO="lvm_end" +ENV{DM_LV_NAME}=="?*_mimage_[0-9]*", GOTO="lvm_end" So your patch is a nice, unintrusive, and pinpointed workaround for karmic, while the real bug is being addressed upstream now. Debian's dk- disks already dropped the lvm/dmsetup rules entirely now, but karmic's dmsetup/mdadm packages do not have sufficient rules yet. Thanks! ** Bug watch added: Debian Bug tracker #545032 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545032 ** Changed in: devicekit-disks (Ubuntu) Importance: Undecided => Medium ** Changed in: devicekit-disks (Ubuntu) Status: New => Triaged ** Changed in: devicekit-disks (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- dk-disks shows internal LVs and Log of mirrored LVM LVs https://bugs.launchpad.net/bugs/458529 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
