"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: Configuration daemon can't speak protocol version

Cause

While attempting to run vxva (the volume manager GUI) with an upgrade from VXVM 2.0 or 2.1 to VXVM 2.3, you receive this 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, that 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.

Most likely you are using the wrong path for vxva. For versions 2.1 and below of vxva, the binary can be 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 normal, since you do not NEED to remove the old package), you probably still have the old /opt/vxva/bin in your $PATH, and, thus, you are attempting to run the older version of vxva.

Action

Run the newer vxva program: /opt/SUNWvxva/bin/vxva. If that remedy does work and you do not get the error message, 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 

Volume too large for defined data type

Cause

This error occurred when trying to open a database file that was greater than 2 Gbytes in size. You should be able to do this, because the Solaris 2.6 release supports file sizes greater than 2 Gbytes.

Action

It is true that the Solaris 2.6 software supports file sizes greater than 2 Gbytes, but to open a file of that size, you must use a new version of the standard calls. There are 64-bit versions of most system calls and libc functions. For example: open64 instead of open.

See Also

Refer to the lf64(5) man page.

vxconfigd error: segmentation fault

Cause

When the system boots, the vxconfigd 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 old (like 1970) or far out in the future (like 2010), vxconfigd core dumps.

Change the date on the system using /bin/date or /usr/bin/date and vxconfigd starts without problems.

vxfs filesystems not mounting

Cause

In this case, the user was unable to mount and was getting uncorrectable error messages from mountall. Below is the individual mount report:

mount: You don't have a license to run this program

Feature name: CURRSET [95]     
Number of licenses: 1 (non-floating)     
Expiration date: Sun Jan 18 03:00:00 1998 (22.8 days from now)     
Release Level: 20     
Machine Class: All      

Feature name: RAID [96]     
Number of licenses: 1 (non-floating)     
Expiration date: Sun Jan 18 03:00:00 1998 (22.8 days from now)     
Release Level: 20     
Machine Class: All

Action

Use vxfsserial -p to see the state of the vxfs license. In this case, it had expired. Unexpired vxfsserial -p output looks similiar to the following:

Feature name: VXFS [80]     
Number of licenses: 1 (non-floating)     
Expiration date: No expiration date     
Release Level: 22     
Machine Class: 934986342

vxvm:vxslicer:ERROR unsupported disk layout

Cause

When trying to encapsulate a disk you receive 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 two 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.