HP-UX 11i Version 1.5 Release Notes, May 2001
Table Of Contents
- 1 Overview of the Release Notes
- 2 Workstation/Server Specific Information
- 3 HP-UX Features
- 4 File and Disk Management
- 5 Networking
- 6 Commands and System Calls
- 7 Programming
- aC++ Libraries
- Changes to libc
- libcres.a Library
- New libdcekt.sl and libdcecpkt.sl Libraries
- New Linux Compatible API Library
- New locale Libraries
- New Unwind Library
- X11 Libraries
- SNMP
- Machine Dependent Headers
- Threadsafe Documentation
- Obsolescence and Deprecation of APIs
- Linker Toolset
- gprof Multiple Shared Library Profiling
- CXperf Performance Monitoring Support
- HP Caliper
- WDB Debugger Tool
- ADB Debugger Tool
- Fortran
- Packaging for Specific Releases
- 8 Other Functionality
File and Disk Management
VERITAS Volume Manager
Chapter 4 65
VxVM DMP Lists Disabled Paths That Have Been Reused
• Problem: When one of multiple paths or cables to a disk array is
disconnected, fails, or is swapped with another path, and then that
same path or cable is reconnected or replaced, it is possible that
HP-UX will recognize the recovered path as a new path, not as the
same path that has simply recovered. In this case, DMP will list twice
as many paths: the “new” ones in the ENABLED state and the “old”
ones (that is, from before the paths were swapped, removed or
replaced) in the DISABLED state. I/O continues to be routed correctly.
• Workaround: None necessary. VxVM DMP will not automatically
clean up the paths that are no longer in use, or that are in the
DISABLED state. When the host is rebooted, the DMP database will be
rebuilt without the DISABLED path definitions.
Run vxdctl enable to Show Status Changes for LVM Disks
• Problem: VxVM output will not reflect status changes for LVM disks
until vxdctl (1M) is run. For example, if you clear an LVM disk with
pvremove (1M), vxdiskadm will still list the status of that disk as
“LVM,” until you run vxdctl enable. This is also true for vmsa
output and the output from other VxVM commands.
• Workaround: Run vxdctl enable after making any changes to LVM
disks to update VxVM’s database.
VMSA Continues Running With No rootdg
• Problem: If rootdg is on an external device which must be shut down,
then VxVM commands won’t run. However, VMSA continues to run,
even though it cannot complete operations.
• Workaround: None.
Duplicate Device Name Creation in rootdg
• Problem: When you create new volumes in therootdg 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