HP 3PAR InForm OS 2.3.1 Extended MU5 Release Notes (QL226-96621, May 2013)
Table 1 Modifications to the InForm OS (continued)
DescriptionItemIssue ID
Due to insufficient throttling of iSCSI host I/O, hosts were able to push a very large
number of I/O requests to the HP 3PAR storage system that could occasionally result
Controller nodes go
offline due to insufficient
iSCSI host I/O throttling.
59578
in a controller node going offline as it took too long to process those requests to send
heartbeat messages in a timely manner. This is resolved by sending back a SCSI
QFULL error condition to a newly received command on an iSCSI port when the
number of pending commands on the port has reached a predetermined limit.
After a master node reboot or system reboot, events from a long time prior could show
up showeventlog again. This is resolved.
Resolved old events
showing up again in CLI
command
showeventlog
59672
Media failures on certain chunklets would sometimes prevent relocation of other
chunklets from the RAID set, as well as returning a preserved LD back to normal. This
is resolved.
REsolved chunklet
relocation after media
failures.
60029
A scheduled task is created to monitor for slow performing drives in the InServ. If a
slow drive is detected, a system alert is generated. This drive is also proactively offlined
and the data vacated if no other failed/degraded drives exist in the Storage System.
Slow drives are not
detected by InForm OS
60207
In situations where there is a heavily loaded system with data-heavy snapshot with
heavily populated meta data tables, when deleting some of these snapshots, the meta
When deleting a large
and filled snapshot can
60494
data tables are traversed causing the CPU to be held for an excessive amount of time.lockup a CPU for a long
period of time. This can prevent other processes/tasks from running and can cause the background
internode comms processing to be delayed, resulting in the erroneous belief that one
of the other nodes has failed. This is resolved and it prevents the CPU from being held
for an excessive amount of time while traversing the meta data tables during snapshot
removal.
It is possible to attempt the removal a VV that had been just removed from an exported
VV set before the VV export is fully cleaned up.
Removal of volume from
exported VV set.
61363
In 2.3.1 MU5 it is now possible to rename a VV without undesirable consequences.Changing the name of a
VV during a Remote
61371
Copy synchronization
could cause a cluster to
go offline.
Using the setvv -snp_cpg command on VVs relying on shared logical disks causes
a panic of the system manager. The behavior of the setvv command is corrected.
CLI command setvv
-snp_cpg behavior
62000
Now all the VVs sharing LDs must be specified as arguments, otherwise the command
will fail.
with shared logical disks
corrected.
Using CreateOrModifyElementFromStoragePool to grow a volume resulted in an error.
This is resolved.
The grow volume
operation via
CreateOrModifyElement
nl
62103
FromStoragePool results
in failure.
The host ID shown in the CLI command showhost -agent incorrectly displays the
internally generated host ID from the HP 3PAR storage system and not the ID reported
Host ID shown in the CLI
command showhost
-agent is incorrect.
62212
by the Host Explorer running on the host. The workaround is to consult the Host Explorer
for the ID.
When the system modifies VV mapping, it modified the VV mapping first and then
allocates memory for new mappings. If the memory allocation is larger than 128 K,
A VV mapping query
causes a node panic
62537
it drops the mutex, which results in node panic if there are queries of VV mappingwhen allocating 128 Kor
during this window. This is resolved by allocating memory before modifying the VV
mapping.
more memory to modify
VV mapping.
The showrsv command and reservation information retrieved by the IMC will no
longer block running other commands.
The showrsv command
will not block other
commands
62564
Under heavy CPU load, sometimes HBA mailbox commands are incorrectly timed out
resulting in the driver taking a firmware core dump and resetting the HBA.
Improve detection of
HBA mailbox timeouts.
63307
HP 3PAR InForm Operating System Release Notes 7