On Tue, Jun 26, 2012 at 02:32:05PM -0400, Mike Snitzer wrote: > The new 'no_partitions' feature serves as a notifier to kpartx to _not_ > create partitions on these multipath devices. This isn't really multipath-specific so doesn't belong in the target. It could go into dm core, but we already have flags attached to udev cookies that can turn udev rules on and off and thereby could allow userspace multipath to control whether or not kpartx creates partitions on any particular device. But first I'd like us to explore creating a config file for kpartx and controlling the behaviour from there. Activation could then be triggered by target type, device name, scsi WWID, dm UUID etc. according to rules in that file. I think this approach of handling each layer independently gives us the best chance of ending up with integrated management of arbitrary device stacks. Alasdair -- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
