All metamembers must belong to the same physical disk group. Metadevices must be composed of devices that are all of the same FBA emulation type.  To adding metamembers into a striped metadevice, all members must be the same size and have the same mirror protection. Making sure you use the protect_data  = true option.
Hi,  What is the criteria to be a candidate for participate in compositoon or become a meta member (in other words, how do i know whether a lun can be added to a meta)? I am interested only in cocantenate and stripe (there is no concatenate+stripe or other meta configurations). Here is my understanding so far. Can any one please confirm or add details?  Input Parameters:  1. Metahead (either concatenate or stripe) (reference to meta head) 2. Lun (reference to a lun/volume/device)  Output:  Determins whether a given lun can be added to given metahead or not (boolan)  If  MetaHead is of concatenate configuration        The given lun should be unbound        Lun should be unmapped        Anything else i should be wary of?  Else If Metahead is of stripe configuration      The given lun should be unbound      It should have the same size as meta member size (as each stripes will have same capacity)      They should have the same RDF capability values      Lun should be unmapped      Anything else i should be wary of? Else      Not supported ("I dont care about this configuration [IMAGE]")  Can any one please confirm or add details if i forget any?  Regards,
Adding a lun (volume/device) to meta: What is the criteria to be a candidate to 
participate in composition (become a meta member)?