HP IO Accelerator Driver and Management Software Version 3.2.3 Release Notes

Change log 14
Change log
3.2.3 change log
This change log documents the changes made from 3.2.2 to 3.2.3, which includes the following:
• HP-UX is not supported with this release.
• Added support for Windows Server 2003. For more information, see "Supported operating systems (on
page 8)."
• Added support for 3.0 TB devices. For more information, see "Supported devices (on page 9)."
• Change to fio-sure-erase so devices maintain current formatting parameters rather than reverting
to the default parameters. Added an option (-t) that resets the device format parameters to the default
settings.
Fixed the following issues:
• Change to default setting of use_workqueue parameter
Issue: When the use_workqueue parameter was changed to a default value of 0 in VSL version
3.2.2, it exposed an issue with certain Linux kernels that resulted in decreased write performance with
file systems and other operations that use Asynchronous IO or libaio and performed FLUSH functions.
Resolution: The issue in these kernels no longer impacts write performance.
• Incorrect load average
Issue: The reported Load average in Linux was incorrect due to a process (fct0-smp) in a constant
state D (reporting a load of 1).
Resolution: Devices now only report a load of 1 while in use.
• Recommendation not to upgrade certain devices
Issue: Read error issue with 320 GB ioDrive and 640 GB ioDrive Duo devices on IO Accelerator VSL
version 3.2.2. This negatively affected read and write activity, and the products might enter reduced
write mode.
Resolution: Restored the behavior of previous releases. HP recommends upgrading those devices to this
IO Accelerator VSL release.
• Powercut issue with Virtual Controller devices
Issue: Powercut feature not working on Virtual Controller devices. Some in-flight data might have been
lost in a power loss event.
Resolution: Powercut feature now works on all Virtual Controller devices. HP recommends upgrading to
this release if you are using Virtual Controller technology.
• Virtual Controller logs reversed
Issue: Virtual Controller operating system event log messages were reversed for splitting and merging.
The devices were split or merged as expected, but the logs were incorrect.
Resolution: Logs indicate splits and merges correctly.
• Virtual Controller conversions failing if unsupported devices installed