Veritas Volume Manager 4.1 Release Notes (5900-0590, March 2010)

To recover these disks, run the vxdarestore command. See “Issues Regarding Persistent
Simple/Nopriv Disks with Enclosure-Based Naming? in the Veritas Volume Manager 4.1
Administrator’s Guide and the vxdarestore (1M) manual page.
• HDS9500V Array Support Library
In VxVM 3.5, support for the Hitachi Data Systems HDS9500V array was provided by the
VRTShds9500v Array Support Library (ASL). If the VRTShds9500v ASL is currently installed
on your VxVM 3.5 system and you are updating to HP-UX 11i v3 use the following command
to remove this ASL before updating to HP-UX 11iv3:
# swremove VRTShds9500v
• VxVM may wrongly calculate the capacity of disks in a MSA30 JBOD
Problem
Due to an issue with the firmware, VxVM may wrongly calculate the capacity of disks in a
MSA30 JBOD. The disk capacity shown by VxVM would be lesser than the actual capacity
of the disk.
Workaround
Upgrade to the latest firmware revision HPB5 or later.
• Disk devices in arrays are not recognized properly
Problem
Enclosures are not recognized as arrays but they are recognized as DISKS.
Workaround
As VxVM 4.1 does not provide ASLs, the arrays are not recognized properly. ASLs are
shipped from VxVM 5.0 and onwards. You must upgrade to VxVM 5.0 for correct device
recognition.
Hot-Relocation Issues
Following data integrity issues are identified:
• Impact of Hot-Relocation on Performance
Problem
Except for rootvol and swapvol, hot-relocation does not guarantee the same layout of
data or performance after relocation.
Workaround
None. After relocation a single subdisk that existed before relocation may be split into two
or more subdisks on separate disks after relocation (if there is not enough contiguous space
on a single disk to accommodate that subdisk).
• Disk Information in Notification Messages
Problem
When a disk failure occurs, the hot-relocation feature notifies the system administrator of
the failure and any relocation attempts, through electronic mail messages. The messages
typically include information about the device offset and disk access name affected by the
failure. However, if a disk fails completely or a disk is turned off, the disk access name and
device offset information is not included in the mail messages.
Workaround
None. This happens because VxVM no longer has access to this information.
Known Problems And Workaround 15