VERITAS Storage Foundation 4.1 Release Notes

Software Issues
32 VERITAS Storage Foundation Release Notes
LUN_SERIAL_NO : 50001FE100270DF0
600508B40010293D00006000012A0000Printing
Name-Value Pair
Printing Name-Value Pair
Printing Name-Value Pair
.
.
.
These messages are harmless and can be ignored.
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. [i14895]
DMP Issues
Usage of dmp_failed_io_threshold Parameter
Data loss can occur after the failure of a single path in a multipathed environment. This might
happen because of an interaction between an Application or file system and Volume Manager. This
issue applies to configurations in which:
◆ VxVM volumes are not mirrored.
◆ There are multiple paths to the disk.
◆ A portion of the I/O path below DMP fails in such a way that the error is not returned to DMP
before 10 minutes have elapsed. Examples of failures that have been seen to cause this
condition, include bad hardware (HBA, FCOT, GBIC, Switch Port, Array Controller) and
HBA reconfigured to retry endlessly.