Peter Rajnoha <prajnoha@redhat.com> writes: > Thanks! Well, sorry for that, I've finally noticed the thing, > that was another bug, unfortunately. Should be solved now with > this git head in lvm2 upstream: > 89d77326170d020ebba6ae1c717c08ac4b07996a > (git.fedorahosted.org/git/lvm2.git) > > Thing is that the pool volume *should always* be marked > as private which also means DM_UDEV_DISABLE_OTHER_RULES_FLAG > is set. Nice, thanks! With this fixed, I have to ask again: Is _every_ situation where a block device goes from public to private with a "change" event a bug? I would say "yes", simply because I can't think of a situation where LVM2 doesn't know from the start whether the device is creates is gonna be public or private. If so, we just keep UDisks2 as it is, I'd say, and I file bugs when I find another public->private transition. _______________________________________________ linux-lvm mailing list linux-lvm@redhat.com https://www.redhat.com/mailman/listinfo/linux-lvm read the LVM HOW-TO at http://tldp.org/HOWTO/LVM-HOWTO/
