I've added the prefix 'LVM-' to the uuids of all devices created by LVM2. This means that it's trivial to identify them as 'belonging' to the lvm2 application. libdevmapper is being extended at the moment to incorporate higher-level functions. One of the new library calls I've added so far is capable of acting on several devices. One of its parameters is a uuid prefix so that it only acts on devices with a matching prefix. This is a simple way of providing application ownership so that LVM2 will never be able to do anything to a device created by multipath-tools, for example. When you list those devices with 'dmsetup' you can tell immediately whether or not LVM2 created them, and easily grep / sort the output. I suggest EVMS, cryptsetup, ddraid, multipath tools etc. also consider adding short application prefixes to the uuids of devices they create. Alasdair -- agk@xxxxxxxxxx -- dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
