Veritas Volume Manager 5.0 Release Notes (5900-0593, March 2010)

Veritas Volume Manager 5.0 Release Notes
Known Issues
Chapter 122
Unlike the VxVM I/O daemons, DMP daemons, which are also kernel threads, appear in
the output from the ps command as they have an associated process table entry. This
difference in behavior is harmless.
Device Issues
• Unsupported disk arrays
To ensure that DMP is set up correctly on a multiported JBOD or other disk array that is
not supported by VxVM, use the procedure given in Adding Unsupported Disk Arrays to
the DISKS Category in the Administering Disks chapter of the Veritas Volume Manager
Administrator’s Guide. Otherwise, VxVM treats the independent paths to the disks as
separate devices, which can result in data corruption.
• Hitachi arrays in Active/Active Mode
When Hitachi DF400 and DF500 arrays are configured in Active/Active mode,
performance is degraded. [i73154]
• Adding HP-EVA disks
When HP-EVA disks are added to VxVM 5.0, debug messages such as the following are
displayed:
# vxdctl enable
Printing Name-Value Pair
CAB_SERIAL_NO : 50001FE100270DF0Printing Name-Value Pair
CAB_SERIAL_NO : Printing Name-Value Pair
Printing Name-Value Pair
Printing Name-Value Pair
CAB_SERIAL_NO : Printing Name-Value Pair
50001FE100270DF0
LUN_SERIAL_NO : 50001FE100270DF0
600508B40010293D00006000012A0000Printing
Name-Value Pair
Printing Name-Value Pair
Printing Name-Value Pair...
These messages are harmless and can be ignored.