|
|
|
|
|
To resolve conflicting configuration information, you must decide which disk contains the correct version of the disk group configuration database. To assist you in doing this, you can run the vxsplitlines command to show the actual serial ID on each disk in the disk group and the serial ID that was expected from the configuration database. For each disk, the command also shows the vxdg command that you must run to select the configuration database copy on that disk as being the definitive copy to use for importing the disk group.
Note
The disk group must have a version number of at least 110.
The following is sample output from running vxsplitlines on the disk group newdg:
The following splits were found in disk group newdg
They are listed in da(dm) name pairs.
The following is sample output from running vxsplitlines on the disk group newdg:
The following splits were found in disk group newdg
They are listed in da(dm) name pairs.
c2t5d0s2 ( c2t5d0s2 ), c2t6d0s2 ( c2t6d0s2 ),
The configuration from any of the disks in this split should appear to be be the same.
To see the configuration from any of the disks in this split, run:
/etc/vx/diag.d/vxprivutil dumpconfig /dev/vx/dmp/c2t5d0s2
To import the dg with the configuration from this split, run:
/usr/sbin/vxdg -o selectcp=1045852127.32.olancha import newdg
To get more information about this particular configuration, run:
/usr/sbin/vxsplitlines -g newdg -c c2t5d0s2
c2t7d0s2 ( c2t7d0s2 ), c2t8d0s2 ( c2t8d0s2 ),
The configuration from any of the disks in this split should appear to be be the same.
To see the configuration from any of the disks in this split, run:
/etc/vx/diag.d/vxprivutil dumpconfig /dev/vx/dmp/c2t7d0s2
To import the dg with the configuration from this split, run:
/usr/sbin/vxdg -o selectcp=1045852127.33.olancha import newdg
To get more information about this particular configuration, run:
/usr/sbin/vxsplitlines -g newdg -c c2t7d0s2
In this example, the disk group has four disks, and is split so that two disks appear to be on each side of the split.
You can specify the -c option to vxsplitlines to print detailed information about each of the disk IDs from the configuration copy on a disk specified by its disk access name:
# vxsplitlines -g newdg -c c2t6d0s2
DANAME(DMNAME) || Actual SSB || Expected SSB
c2t5d0s2( c2t5d0s2 ) || 0.1 || 0.0 ssb ids don't match
c2t6d0s2( c2t6d0s2 ) || 0.1 || 0.1 ssb ids match
c2t7d0s2( c2t7d0s2 ) || 0.1 || 0.1 ssb ids match
c2t8d0s2( c2t8d0s2 ) || 0.1 || 0.0 ssb ids don't match
Please note that even though some disks ssb ids might match
that does not necessarily mean that those disks' config copies
have all the changes. From some other configuration copies, those disks' ssb ids might not match.
To see the configuration from this disk, run
/etc/vx/diag.d/vxprivutil dumpconfig /dev/vx/dmp/c2t6d0s2
Based on your knowledge of how the serial split brain condition came about, you must choose one disk's configuration to be used to import the disk group. For example, the following command imports the disk group using the configuration copy that is on side 0 of the split:
# /usr/sbin/vxdg -o selectcp=1045852127.32.olancha import newdg
When you have selected a preferred configuration copy, and the disk group has been imported, VxVM resets the serial IDs to 0 for the imported disks. The actual and expected serial IDs for any disks in the disk group that are not imported at this time remain unaltered.