Leon, If the 51th disk contains a volume (metadevice is built on the disk), it will be imported correctly. The scenario described below is only applicable to disks with no mddb and not part of any metadevices, thus, doesn't make sense to import into the diskset. Does that help?
-tony Leon Koll wrote: > The manual says: [i]The metaimport command also does not import a disk in a > disk set if the disk does not contain a volume or a state database replica. > This scenario occurs if a volume or a state database replica have not been > added to a disk or have been deleted from a disk. > In this case, when you import the disk set to another system, you would find > that the > disk is missing from the disk set. For example, maximum of 50 state database > replicas are allowed per Solaris Volume Manager disk set. If you have 60 > disks in a disk set, the 10 disks that do not contain a state database > replica must contain a volume in order to be imported with the disk set.[/i] > What should I do with the disk #51 that doesn't have a state database replica > ? > This message posted from opensolaris.org > _______________________________________________ > lvm-discuss mailing list > lvm-discuss at opensolaris.org
