VERITAS Volume Manager 4.1 Troubleshooting Guide

Error Messages
Understanding Messages
Chapter 6 87
V-5-1-571
VxVM vxconfigd ERROR V-5-1-571 Disk group group, Disk disk: Skip disk group with
duplicate name
• Description: Two disk groups with the same name are tagged for auto-importing by the
same host. Disk groups are identified both by a simple name and by a long unique
identifier (disk group ID) assigned when the disk group is created. Thus, this error
indicates that two disks indicate the same disk group name but a different disk group ID.
VxVM does not allow you to create a disk group or import a disk group from another
machine, if that would cause a collision with a disk group that is already imported.
Therefore, this error is unlikely to occur under normal use. However, this error can occur
in the following two cases:
— A disk group cannot be auto-imported due to some temporary failure. If you create a
new disk group with the same name as the failed disk group and reboot, the new disk
group is imported first. The auto-import of the older disk group fails because more
recently modified disk groups have precedence over older disk groups.
— A disk group is deported from one host using the -h option to cause the disk group to
be auto-imported on reboot from another host. If the second host was already
auto-importing a disk group with the same name, then reboot of that host will yield
this error.
• Action: If you want to import both disk groups, then rename the second disk group on
import. See the vxdg(1M) manual page for information on how to use the import operation
to rename a disk group.
V-5-1-577
VxVM vxconfigd WARNING V-5-1-577 Disk group group: Disk group log may
be too small
Log size should be at least number blocks
• Description: The log areas for the disk group have become too small for the size of
configuration currently in the group. This message only occurs during disk group import;
it can only occur if the disk was inaccessible while new database objects were added to the
configuration, and the disk was then made accessible and the system restarted. This
should not normally happen without first displaying a message about the database area
size.