From what you wrote, it seems you're using libdevmapper directly to set
up the mapping, right?
We *should* be using libdevmapper directly. We'll certainly do that before we show our code to anyone else :-)
The important flags to avoid scanning within udev rules (blkid and
similar calls there) is the DM_UDEV_DISABLE_DISK_RULES_FLAG (this is to
disable the blkid call in 13-dm-disk.rules and associated symlink
creation) and also DM_UDEV_DISABLE_OTHER_RULES_FLAG to disable all the
other foreign non-dm udev rules - this is a flag that other rules
(should) check to skip processing if they see it.
I had a suspicion that this was going to involve udev rules. This should be enough to get us started.
This is only general information on how device-mapper with libdm
interacts with udev. To help you more, I'd probably need more detailed
look at your usecase, design and goals you need to achieve so feel free
to contact me...
Will do. Thanks again.
..................................................................... Northeastern Computer & Information Science (617) 373-8683
|
--
dm-devel mailing list
dm-devel@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/dm-devel
