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

Veritas Volume Manager 5.0 Release Notes
Known Issues
Chapter 1 23
Hot-Relocation Issues
• Impact of hot-relocation on performance
Except for rootvol and swapvol, hot-relocation does not guarantee the same layout of data
or performance after relocation. It is therefore possible that 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).
[i14894]
• Disk information in notification messages
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. This is because VxVM no
longer has access to this information. [14895]
Cluster Functionality Issues
NOTE Cluster support is not available with the current release of VxVM 5.0.
• Node rejoin causes I/O failures with A/PF arrays
A cluster node should not be rejoined to a cluster if both the primary and secondary paths
are enabled to an A/PF array, but all the other nodes are using only the secondary paths.
This is because the joining node does not have any knowledge of the cluster configuration
before the join takes place, and it attempts to use the primary path for I/O. As a result, the
other cluster nodes can experience I/O failures and leave the cluster.
Workaround:
1. Before joining the node to the cluster, disconnect the cable that corresponds to the
primary path between the node and the array.
2. Check that the node has joined the cluster by using the following command:
# vxclustadm nidmap
The output from this command should show an entry for the node.
3. Reconnect the cable that corresponds to the primary path between the node and the
array.
4. Use the following command to trigger cluster-wide failback: