Use this procedure if a disk set is corrupted or in a state that the nodes in the cluster are unable to take ownership of the disk set. If your attempts to clear the state have failed, use this procedure as a last attempt to fix the disk set.
These procedures work for Solaris Volume Manager metasets and multi-owner Solaris Volume Manager metasets.
Restoring a disk set from scratch can be time-consuming and error prone. A better alternative is to use the metastat command to regularly back up replicas or use Oracle Explorer (SUNWexplo) to create a backup. You can then use the saved configuration to recreate the disk set. You should save the current configuration into files (using the prtvtoc and metastat commands), and then recreate the disk set and its components. See How to Recreate the Solaris Volume Manager Software Configuration.
# /usr/sbin/prtvtoc /dev/global/rdsk/disk-name > /etc/lvm/disk-name.vtoc
# /bin/cp /etc/lvm/md.tab /etc/lvm/md.tab_ORIGINAL # /usr/sbin/metastat -p -s set-name >> /etc/lvm/md.tab
Purging a set from a node or all nodes removes the configuration. To purge a disk set from a node, the node must not have ownership of the disk set.
# /usr/sbin/metaset -s set-name -P
Running this command removes the disk set information from the database replicas, as well as the Oracle Solaris Cluster repository. The –P and –C options allow a disk set to be purged without the need to completely rebuild the Solaris Volume Manager environment.
# /usr/cluster/lib/sc/dcs_config -c remove -s set-name
For more information, see the dcs_config(1M) man page.
# /usr/sbin/metaset -s set-name -C purge
You should generally use the –P option, rather than the –C option. Using the –C option can cause a problem recreating the disk set because the Oracle Solaris Cluster software still recognizes the disk set.
# /usr/cluster/lib/sc/dcs_config -c remove -s setname
If the purge options fail, verify that you installed the latest kernel and metadevice updates and contact My Oracle Support.
Use this procedure only if you experience a complete loss of your Solaris Volume Manager software configuration. The steps assume that you have saved your current Solaris Volume Manager configuration and its components and purged the corrupted disk set.
# /usr/sbin/metaset -s set-name -a -h node1 node2
If this is a multi-owner disk set, use the following command to create a new disk set.
/usr/sbin/metaset -s set-name -aM -h node1 node2
/usr/sbin/metaset -s set-name -a -m node1 node2
/usr/sbin/metaset -s set-name -a /dev/did/rdsk/disk-name /dev/did/rdsk/disk-name
However, if you are recreating a set to recover, you should format the disks according to a saved configuration in the /etc/lvm/disk-name.vtoc file. For example:
# /usr/sbin/fmthard -s /etc/lvm/d4.vtoc /dev/global/rdsk/d4s2
# /usr/sbin/fmthard -s /etc/lvm/d8.vtoc /dev/global/rdsk/d8s2
You can run this command on any node.
# /usr/sbin/metainit -s set-name -n -a metadevice
# /usr/sbin/metainit -s set-name -a metadevice
# /usr/sbin/fsck -n /dev/md/set-name/rdsk/metadevice
If the fsck command displays only a few errors, such as superblock count, then the device was probably reconstructed correctly. You can then run the fsck command without the –n option. If multiple errors appear, verify that you reconstructed the metadevice correctly. If you have, review the fsck errors to determine if the file system can be recovered. If it cannot, you should restore the data from a backup.
# /usr/sbin/metastat -p >> /etc/lvm/md.tab