http://bugzilla.novell.com/show_bug.cgi?id=598193 http://bugzilla.novell.com/show_bug.cgi?id=598193#c64 --- Comment #64 from Kay Sievers <kasievers@novell.com> 2010-06-22 09:47:26 UTC --- (In reply to comment #63)
Kay, what do you suggest as short-time workaround for 11.3?
Unfortunately, I can not suggest any straight-forward workaround. I guess, the current device-mapper/lvm code we currently ship can not work as expected, it is making assumptions about uevents which are not met on common systems (see the bugs at the end).
We have RC2 next week and your comment #60 does not seem to answer #59 (at least in my understanding).
I tried to say: "the label,uuid-symlinks are usually _not_ updated for dm devices when filesystem metadata is changed. Device-mapper devices are excluded from udev's logic, because they don't behave as expected" and "using artificial events for device-mapper devices, like libstorage does, will break the current device-mapper/lvm assumptions" Which unfortunately means, with the current code, we have no simple solution for the problem. It's all work-in-progress upstream, and the lvm git repo has added a few workarounds (which we don't ship) for the most common problems: http://sourceware.org/git/?p=lvm2.git;a=blob;f=udev/10-dm.rules.in;h=0db8809... But all this is likely not well tested, and might also not fully work as expected. I guess we have only two options: to update to the current dm/lvm code or go back to the old version which does not plug into udev. But I really don't know enough about device-mapper/lvm to make a decision here. The latest comments in the corresponding Red Hat bugs seem to state that the issues are addressed: https://bugzilla.redhat.com/show_bug.cgi?id=561425 https://bugzilla.redhat.com/show_bug.cgi?id=577798 -- 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.