[linux-lvm] Identifying useable block devices

Peter Rajnoha prajnoha at redhat.com
Fri Jan 24 15:08:17 UTC 2014

On 01/24/2014 03:50 PM, Marius Vollmer wrote:
> Peter Rajnoha <prajnoha at 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?

Hmm, and if we can detect a device going from public to private, would
it be a problem to detect the other way round - a device going from
private to public? IMHO it would be exactly the same situation - just
in case it gets public, the device would be presented to any event
listeners again with all the context it currently has.


More information about the linux-lvm mailing list