On Fri, Mar 19, 2010 at 14:24, Peter Rajnoha <prajnoha@xxxxxxxxxx> wrote: > On 03/19/2010 10:24 AM, Kay Sievers wrote: >> No, that's what "change" is for, and we already have these "change" >> events for dm. Udev does not care if the device is ready or not, it >> synchronizes /sys and /dev, and that works just fine with "change" >> events. > > CHANGE events, not quite... We can't even rely on these. > > Just to mention, there's also a CHANGE event generated when > read-only flag is set for a device (this is not managed by > device-mapper of course). This one is generated even before > the actual CHANGE event that is generated when DM device is > ready to be used. Sure, but as mentioned earlier, these events are just expected to fail, and update the current udev state, if they can't retrieve the needed information or find out that the device in not usable. Kay -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
