HP 4400 HP StorageWorks Enterprise Virtual Array Release Notes (XCS 09531000) - Page 4

Fixes

Get HP 4400 PDF manuals and user guides View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 4 highlights

Fixes The following issues have been fixed in XCS 09531000: Controller termination This section describes issues that can result in termination of controller operation. A single controller termination will result in a reduction of redundancy. A dual controller termination indicates a possibility of a data unavailable condition. A recursive termination will require manual intervention to address. • Improperly processed SCSI commands (such as READ or Mode Sense commands) from some host applications to LUN 0 (which is designated as the Storage Array Controller Device (SACD)) on the EVA could cause controller terminations (termination code 0x0403047f). • Improved code tracking capability to address the situation of both controllers terminating due to the host port update process. • Corrected the following situations in which a controller termination could occur: • After the expansion of a virtual disk if a read request was sent to an unallocated space on the virtual disk before the expansion had completed (termination code 0x0442011f or 0x04800106). • After a device port failure, causing a dual controller termination (termination code 0x0205010a). • When a persistent LUN reservation was requested and a related metadata I/O failed as the result of a back-end issue (termination code 0x075b0100). • When upgrading an EVA4400 HSV300-S embedded switch controller (termination code 0x04d3011f). • Due to the depletion of inter-controller resources (termination code 0x42280102 or 0x421c0101). • When a controller failover is interrupted (termination code 0x020a0104). • Due to a null pointer exception (termination code 04d3011f). • After a cache metadata corruption and cache failover does not occur when transitioning an inoperative virtual disk (termination code 0x020d0104). • After an occurrence of a TSDK ASSERT when the controller is unable to determine the link status from a back-end device during a host load (termination code 0x065a010e). • When medium errors were encountered during the processing of DR logs (termination code 0x075b0104). • Due to an interruption in the leveling of a disk group (termination code 0x0402011f). Disks (disk groups, virtual disks) This section describes issues affecting physical and virtual disks or disk groups, which can lead to a range of behaviors including a loss of redundancy, performance impact, or data unavailability. • A data migration operation stalled after a disk drive error occurred. • The one minute delay that occurred prior to a controller resynchronization (due to a RAID1 inop- erative state) has been removed. • Improved the storage of LUN world wide name IDs in persistent memory. • Data and non-data exchange timeout processing has been changed to reduce erroneous Single Port on Fibre (SPOF) reporting during high workload conditions. • Improved the sequential disk leveling process. 4

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
Fixes
The following issues have been fixed in XCS 09531000:
Controller termination
This section describes issues that can result in termination of controller operation. A single controller
termination will result in a reduction of redundancy. A dual controller termination indicates a possibility
of a data unavailable condition. A recursive termination will require manual intervention to address.
•
Improperly processed SCSI commands (such as READ or Mode Sense commands) from some host
applications to LUN 0 (which is designated as the Storage Array Controller Device (SACD)) on
the EVA could cause controller terminations (termination code
0x0403047f
).
•
Improved code tracking capability to address the situation of both controllers terminating due to
the host port update process.
•
Corrected the following situations in which a controller termination could occur:
•
After the expansion of a virtual disk if a read request was sent to an unallocated space on the
virtual disk before the expansion had completed (termination code
0x0442011f
or
0x04800106
).
•
After a device port failure, causing a dual controller termination (termination code
0x0205010a
).
•
When a persistent LUN reservation was requested and a related metadata I/O failed as the
result of a back-end issue (termination code
0x075b0100
).
•
When upgrading an EVA4400 HSV300-S embedded switch controller (termination code
0x04d3011f
).
•
Due to the depletion of inter-controller resources (termination code
0x42280102
or
0x421c0101
).
•
When a controller failover is interrupted (termination code
0x020a0104
).
•
Due to a null pointer exception (termination code
04d3011f
).
•
After a cache metadata corruption and cache failover does not occur when transitioning an
inoperative virtual disk (termination code
0x020d0104
).
•
After an occurrence of a
TSDK ASSERT
when the controller is unable to determine the link
status from a back-end device during a host load (termination code
0x065a010e
).
•
When medium errors were encountered during the processing of DR logs (termination code
0x075b0104
).
•
Due to an interruption in the leveling of a disk group (termination code
0x0402011f
).
Disks (disk groups, virtual disks)
This section describes issues affecting physical and virtual disks or disk groups, which can lead to a
range of behaviors including a loss of redundancy, performance impact, or data unavailability.
•
A data migration operation stalled after a disk drive error occurred.
•
The one minute delay that occurred prior to a controller resynchronization (due to a RAID1 inop-
erative state) has been removed.
•
Improved the storage of LUN world wide name IDs in persistent memory.
•
Data and non-data exchange timeout processing has been changed to reduce erroneous Single
Port on Fibre (SPOF) reporting during high workload conditions.
•
Improved the sequential disk leveling process.
4