"V"

Value too large for defined data type

Cause

The user ID or group ID of an IPC object or file system object was too large to be stored in an appropriate member of the caller-provided structure.

Action

Run the application on a newer system, or ask the program's author to fix this condition.

Technical Notes

This error occurs only on systems that support a larger range of user or group ID values than a declared member structure can support. This condition usually occurs because the IPC or file system object resides on a remote machine with a larger value of type uid_t, off_t, or gid_t than that of the local system.

The symbolic name for this error is EOVERFLOW, errno=79.

Volume Manager reports error:

Cause

After upgrading from VxVM 2.0 or 2.1 to 2.3, when attempting to run vxva, the volume manager GUI, you get the message:

        Volume Manager reports error:
           Configuration daemon can't speak protocol version

This message indicates that there is a version mismatch between the version of the volume manager daemon (vxconfigd) and the GUI (vxva) you are trying to run. For example, you are running the 2.3 version of vxconfigd, and trying to run an old (2.1) version of vxva.

The most likely reason for this to happen is because the you are using the wrong path for vxva. For vxva versions 2.1 and below, the binary was found in /opt/vxva/bin, but starting with 2.1.1, the location was changed to /opt/SUNWvxva/bin.

If you did not remove the old SUNWvxva package before installing the new 2.3 version (which is a normal thing; you don't NEED to remove the old package), you probably still have the old /opt/vxva/bin in your $PATH, and thus, you're attempting to run the older version of vxva.

Action

Run the newer vxva program: /opt/SUNWvxva/bin/vxva. If that does work and you do not get the error message, simply remove /opt/vxva/bin/vxva from your path statement or remove the old version of vxva and create a symbolic link to the new version with the following two commands:

 
# rm /opt/vxva/bin/vxva 
# ln -s /opt/SUNWvxva/bin/vxva /opt/vxva/bin/vxva 

vxconfigd error: segmentation fault

Cause

When the system boots, the vxconfid fails to start. It fails with a segmentation fault (core dump).

	vxconfigd error: segmentation fault
	[ vxvm warning: _illegal vminor encountered ]

Action

Check the date on the system using date(1) (/bin/date or /usr/bin/date). If the date on the system is very old (like 1970) or very far out in the future (like 2010), vxconfigd core dumps.

Change the date on the system using /bin/date or /usr/bin/date and the vxconfigd will start like a champ.

vxvm:vxslicer:ERROR unsupported disk layout

Cause

When trying to encapsulate a disk you get this error.

Action

You must meet the minimum requirements to encapsulate a disk:

1. You must have two free, zero length, slices on the disk (no cylinders should be assigned to these slices.)

2. You must have two free cylinders on the disk. These 2 cylinders must not be in use by any slice other than slice two.

3. The two free cylinders must be located at the beginning or end of the drive.