VERITAS Volume Manager 3.2 for HP-UX Release Notes

Known Problems and Workarounds

Chapter 1 25

vxassist Command Does not Add a Mirror and a Log

• Problem: The vxassist command does not add a mirror and a log when processing a

command such as the following

# vxassist mirror volume layout=log ...

The mirror is added, but the log is silently omitted.

• Workaround: If a log and a mirror are to be added, add the mirror and the log in two

separate vxassist invocations, as follows

# vxassist mirror volume ...

# vxassist addlog volume ...

vxrecover Needs at Least One ACTIVE or CLEAN Plex to Start a

Volume

• Problem: 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.

• Workaround: 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.

Free Space Reported Differently

• Problem: vxdg free reports free space differently than vxprint -ht.

• Workaround: None.

Resizing Layered Volumes Fails while Resynchronization is Ongoing.

• Problem: Due to the current implementation to handle the resize of layered volumes, it is

recommended that you do not grow or shrink layered volumes (stripe-mirror,

concat-mirror, and so on) while resynchronization is ongoing.

Internally, VxVM converts the layout of layered volumes and updates the configuration