6.2.4 HP StoreAll Storage Release Notes (AW549-96071, April 2013)

Fixes
Fixes in the 6.2.4 release
Firmware release version 1.42 provides the following enhancements:
The timeout for READ CAPACITY commands was increased to 45 seconds. Previously, certain
drive models would be identified as FAILED shortly after a replacement drive was inserted
(if the response time exceeded 15 seconds).
Fixed regressions introduced in firmware version 1.40 that caused the controller to occasionally
hang during replacement drive insertion.
Fixes in the 6.2.3 release
The firmware bundle includes new firmware version 1.40 for the X9720 storage controllers
(ExDS9100cc). Version 1.40 contains critical fixes and is a mandatory upgrade. After updating
the storage controllers to version 1.40, it may take 10-12 minutes for the storage controllers to
complete a reset and restart with the new firmware. During this time, issuing the command
hpsp_fmt --flashrec for the storage_ctlr component might report missing devices. Users
should wait until both controllers restart (with the new firmware) before performing any other
operations on these controllers.
NOTE: The X9720 storage controller firmware version 1.40 has a known issue that could cause
instability, including controller hang, when a replacement drive is inserted. The issue can result
in one or more file system segments going offline. Customers that encounter the issue should
contact HP Support for the recovery procedure.
Fixed an error counter issue (the number of errors did not match the number of corrections) in
ibdircheck. Now, the error counter is increased once (instead of twice) when ibdircheck
finds and fixes a problematic dentry.
ibdircheck no longer deletes a freshly-resolved migrated hard link. Previously, if a problematic
dentry was successfully resolved by lookup, ibdircheck did not check the dentry again and
the dentry may be accidentally deleted.
During inode creation, the inode is now checked to see if it is a replica. This prevents inode
creation from failing due to the inode quota limit being exceeded.
8 Fixes