vxsplitlines - show disks with conflicting configuration copies in a cluster

vxsplitlines [-g diskgroup] [-v]

If you import portions of a disk group on different systems, this can lead to conflicting configuration copies on the disks of the disk group.

If the configuration information in a disk group is ambiguous, it may not be possible for Veritas Volume Manager to determine which configuration copy is most up-to-date. (This is usually termed a serial split brain (SSB) condition when it occurs in a cluster.) You cannot import a disk group in this state unless you specify which disk’s configuration copy to use.

Use the vxsplitlines command to see which disks in a disk group have conflicting configuration copies. and use this information together with your knowledge of the history of the disk groups’ usage to determine which configuration copy is most valid.

The vxsplitlines command displays information about two pools of disks. Disks belonging to the first pool have the same configuration copies while disks belonging to the second pool may not have the same configuration copies.

The output from vxsplitlines displays the vxdg commands that you can run to import the disk group using the available configuration copies. The output suggests a remedial import option for each pool. Choose one of the options to resolve the serial split brain situation. Consider the information that is displayed in the output, such as the number of disks in each pool, when you make your decision.

-g diskgroup	Specifies the disk group. If a disk group is not specified, the default disk group is used as determined from the rules on the vxdg(1M) manual page.
-v	Specifies verbose output. vxsplitlines displays additional disk information in each pool which consists of the disk media name, disk access name, the disk private path and the diskid. It also displays the commands that you can execute to see the configuration copy from each disk using the disk private path.

To display information about the configuration copies for the disk group, mydg, with the serial split brain condition:

vxsplitlines -g mydg

This command displays output such as the following:

VxVM vxsplitlines NOTICE V-0-0-0 There are 2 pools
All the disks in the first pool have the same config copies
All the disks in the second pool may not have the same config copies
Number of disks in the first pool: 1
Number of disks in the second pool: 1
To import the diskgroup with config copy from the first pool
issue the command
 /usr/sbin/vxdg (-s) -o selectcp=1215378871.300.vm2850lx13 import mydg
To import the diskgroup with config copy from the second pool
issue the command
 /usr/sbin/vxdg (-s) -o selectcp=1215378869.294.vm2850lx13 import mydg

To display additional information about the configuration copies for the disks in each pool, use the verbose option:

vxsplitlines -v -g mydg

This command displays output such as the following:

VxVM. vxsplitlines NOTICE V-0-0-0 There are 2 pools
All the disks in the first pool have the same config copies
All the disks in the second pool may not have the same config copies
To see the configuration copy from a disk issue the command
/etc/vx/diag.d/vxprivutil dumpconfig <private path>
To import the diskgroup with config copy from a disk
issue the command
/usr/sbin/vxdg (-s) -o selectcp=<diskid> import mydg
                             Pool 0
DEVICE    DISK      DISK ID                     DISK PRIVATE PATH
mydg1     sdp       1215378871.300.vm2850lx13   /dev/vx/rdmp/sdp5



                             Pool 1
DEVICE    DISK      DISK ID                     DISK PRIVATE PATH
mydg2     sdo       1215378869.294.vm2850lx13   /dev/vx/rdmp/sdo5

The vxsplitlines is primarily intended to be used with private disk groups, but it also works with shared disk groups.

The version number of the disk group must be 110 or greater.

vxdg(1M)

Storage Foundation Administrator’s Guide