I see dmraid has two options -p (no_partitions) and -Z (rm_partitions). I see that rm_partitions does just that, but it's not clear to me what the no_partitions option does. Can somebody explain please?
How do utilities detect that a device is in use by DM? I would like to be able to prevent creation of partitions on any disks my mapping target is using. Are there ways to do that? It would seem that DM solutions like raid, multipath, etc. would require this capability.On Fri, Aug 2, 2013 at 6:07 AM, Zdenek Kabelac <zkabelac@xxxxxxxxxx> wrote:
Dne 1.8.2013 19:04, John Strange napsal(a):In lvm2 it's solved in a way - that we use special flags for udev to avoid
two questions:
1. I'd like to use DM with a new target type. I'm porting our virtualized
storage solution from Windows. I've been able to register my target and get
callbacks working, but in looking at the dm-raid code, I'm concerned with how
tightly coupled it is with the routines in md.c (multiple devices
implementation). Is there an expectation that a DM target use the md_xxxx
routines?
2. I used dmsetup to create a mapping for a device that my target controls.
Is there a way to make the underlying device (e.g. /dev/sdb) not visible to
the system? I'm paranoid about external accesses to a LUN that I'm using.
some scanning/watchrules - however all device are always available through /dev/mapper but user visible devices are accessible via /dev/vg/lv name which is the only suggested and supported way to use LVs.
Obviously we often get reports where users are directly playing with /dev/dm-XXX devices or /dev/mapper/vg-lv in their scripts and configs...
But you can't hide existing devices in system from userland visibility.
Zdenek
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
