VERITAS Volume Manager 4.1 Release Notes (5900-0591, March 2010)

VERITAS Volume Manager 4.1 Release Notes
Known Problems and Workarounds
Chapter 138
Volumes Not Started Following a Reboot
During very fast boots on a system with many volumes, vxconfigd may not be able to
auto-import all of the disk groups by the time vxrecover -s is run to start the volumes. As a
result, some volumes may not be started when an application starts after reboot.
Workaround: Check the state of the volumes before starting the application, or place a sleep
(sleep sec) before the last invocation of vxrecover.
Forcibly Starting a Volume
The vxrecover command starts a volume only if it has at least one plex that is in the ACTIVE
or CLEAN state and is not marked STALE, IOFAIL, REMOVED, or NODAREC. If such a plex
is not found, VxVM assumes that the volume no longer contains valid
up-to-date data, so the volume is not started automatically. A plex can be marked STALE or
IOFAIL as a result of a disk failure or an I/O failure. In such cases, to force the volume to
start, use the following command:
# vxvol -f start volume
However, try to determine what caused the problem before you run this command. It is likely
that the volume needs to be restored from backup, and it is also possible that the disk needs to
be replaced.
Failure of Memory Allocation
On machines with very small amounts of memory (32 megabytes or less), under heavy I/O
stress conditions against high memory usage volumes (such as RAID-5 volumes), a situation
occurs where the system cannot allocate physical memory pages any more.
Messages About VVR Licenses
The following messages may get displayed on the console during a system reboot or during
VxVM initialization when you are running vxinstall:
No VVR license installed on the system; vradmind not started
No VVR license installed on the system; in.vxrsyncd not started
These messages are informational only, and can be safely ignored if you are not a VERITAS
Volume Replicator (VVR) user.