VERITAS Volume Manager 3.5 Release Notes (August 2003)

VERITAS Volume Manager™ HP-UX 11i v2 Release Notes
Patches and Fixes in This Version
Chapter 1 41
Some older Quantum disks (models PD210S and PD425S) do not
respond properly to SCSI inquiry command when the device is in
certain states. As a consequence, these devices are not recognized by
VxVM and, as such, cannot be used as disks for VxVM. A vxdisk
command may list the device in error state or may not list at all.
• Workaround: Do not attempt to define the device for VxVM.
Duplicate Device Name Creation in rootdg
• Problem: When you create new volumes in the rootdg disk group, two
sets of device nodes are created: under both /dev/vx/[r]dsk/ and
/dev/vx/[r]dsk/rootdg. Although either path can be used for mkfs(1M)
or mount(1M), the duplicate sets of device node names can be
confusing.
• Workaround: We recommend using the full pathname to rootdg disk
devices in command line arguments. This is consistent with the
naming of device nodes in other disk groups. For example, to mount a
rootdg volume use:
# mount -F vxfs /dev/vx/dsk/rootdg/vol01 /vol01
Do not use /dev/vx/dsk/vol01 as the pathname.
VEA always uses the full pathname.
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.