http://bugzilla.novell.com/show_bug.cgi?id=598193 http://bugzilla.novell.com/show_bug.cgi?id=598193#c71 Xinwei Hu <xwhu@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO InfoProvider| |kasievers@novell.com --- Comment #71 from Xinwei Hu <xwhu@novell.com> 2010-06-23 09:16:39 UTC --- (In reply to comment #68)
(In reply to comment #67)
This bug is about that rules for device-mapper doesn't work with artificial 'add' event.
It's the case for every event including 'change', not only 'add'.
This is still true with the latest update, and I think it'll be true in foreseeable future.
This sounds different: https://bugzilla.redhat.com/show_bug.cgi?id=561425#c16
No, it's not. At least not in the git repo yet.
So, I think the suggestion in comment#59 is the right step to go.
It might only avoid one of a bunch of cases, where this will go wrong and lead to the removal of dm/lvm symlinks?
Well, I tried again to submit an update of lvm2 into Base:System. The new udev rule works like this: -> If 'add' triggered by libdevmapper, /dev/dm-* will not be removed, but all symlinks will be removed -> If 'change' triggered by libdevmapper, /dev/dm-* and all symlinks will be created. -> If 'add|change' triggered by other source, /dev/dm-* will not be removed, all symlinks will be created according to the info from IMPORT{db}. I'd like to know if this is OK from udev's point of view. If it's OK, I'll try to make this upstream then. Thanks. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.