On 03/12/2014 02:14 PM, Hannes Reinecke wrote: > _However_: The 'no_partition' feature has the advantage that you > don't need to modify the multipath code; it'll just take whatever is > in 'features' and pass it 1:1 into the device-mapper table. > But you still need some config file in userspace that will store the fact that some of the mpath devs need to be marked with this feature flag. > When using cookies for that we'd need either a separate > mechanism/flag for multipathing or filter out the features list. > _And_ we need to modify libdevmapper _and_ multipath at the same > time to make that work. > But if you insist ... If this is a subsystem specific (in this case mpath) flag, we don't need to change libdevmapper, only mpath userspace code. > > So can you make a patch for libdevmapper to add this cookie flag? > I'll be checking the multipath-tools code ... I'll try to think about this a bit more since it would be beneficial to have such a thing for all block devices actually - any of them can be be used in a VM and we need to prevent scanning all such devices, not just mpath ones. A simple solution would be for users to define a udev rule (providing them a template) where they can match against some properties (e.g. DM name, uuid or WWID or whatever else is present for the block dev to match against in the rule). This actually brings us to a general problem with making the device "private" in some way on the host system. AFAIK we still don't have a general rule for this! Everybody is patching this on his own. With all the support for various autoactivations and automounts, this can become quite dangerous then if not configured properly by each subsystem's mechanism to make the device private. -- Peter -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
