VERITAS Volume Manager 3.5 Troubleshooting Guide (September 2004)

Error Messages

vxdg Error Messages

Chapter 3

• Action: Objects speciﬁed for a disk group move, split or join must be either disks or

top-level volumes.

vxvm: vxdg: ERROR: diskdevice: Request crosses disk group boundary

• Description: The speciﬁed disk device is not conﬁgured in the source disk group for a

disk group move or split operation.

• Action: Correct the name of the disk object speciﬁed in the disk group move or split

operation.

vxvm: vxdg: ERROR: diskgroup: split failed: Error in cluster processing

• Description: The host is not the master node in the cluster.

• Action: Perform the operation from the master node.

vxvm: vxdg: ERROR: Transaction already in progress

• Description: One of the disk groups speciﬁed in a disk group move, split or join

operation is currently involved in another unrelated disk group move, split or join

operation (possibly as the result of recovery from a system failure).

• Action: Use the vxprint command to display the status of the disk groups involved. If

vxprint shows that the TUTIL0 ﬁeld for a disk group is set to MOVE, and you are

certain that no disk group move, split or join should be in progress, use the vxdg

command to clear the ﬁeld as described in Chapter 1, “Recovery from Hardware

Failure,” on page 9. Otherwise, retry the operation.

vxvm: vxdg: ERROR: volume: Volume or plex device is open or mounted

• Description: An attempt was made to perform a disk group move, split or join on a

disk group containing an open volume.

• Action: It is most likely that a ﬁle system conﬁgured on the volume is still mounted.

Stop applications that access volumes conﬁgured in the disk group, and unmount

any ﬁle systems conﬁgured in the volumes.

vxvm: vxdg: ERROR: vxdg join sourcedg targetdg failed

vxvm: vxdg: ERROR: object: Record already exists in disk group

• Description: A disk group join operation failed because the name of an object in one

disk group is the same as the name of an object in the other disk group. Such name

clashes are most likely to occur for snap objects and snapshot plexes.

• Action: Use the following command to change the object name in either one of the

disk groups:

# vxedit -g diskgroup rename old_name new_name

For more information about using the vxedit command, see the vxedit(1M) manual

page.

vxvm: vxdg: ERROR: vxdg listmove sourcedg targetdg failed

vxvm:vxdg: ERROR: diskname : Disk not moving, but subdisks on it are

• Description: Some volumes have subdisks that are not on the disks implied by the

supplied list of objects.

• Action: Use the -o expand option to vxdg listmove to produce a self-contained list of

objects.