Duplicating a device only copies configuration, data member count, emulation, capacity of device, disk group info from the source device...

It does not copy the mapping n masking info

regards,

Saurabh

So basically even if a device is bound to a pool, the new device will be unbound. Is there any better way to create target devices for cloning, am i in the right direction?

correct, it will be unbound but at least you don't have to manually build meta members (if it's a meta). You are in the right direction, by using the copy option it will build identical devices except for the things we mentioned above.

The copy dev command does indeed copy the device binding (it will bind the new device to the same pool as the copied device). At least last I tried it this is how it worked for me.

for thin devices i will not copy pool binding, allocation parameters .etc.

correction, for me device was bound but not fully allocation as my source device.

looks like copy option does not work if devices have RDF attributes and are actually in an RDF relationship, bummer.