6.1.5 HP StoreAll Storage Release Notes (AW549-96064, April 2013)

The online upgrade script was fixed to prevent the upgrade from failing when the file system was
unmounted, which previously resulted in no error being displayed and the system being partially
upgraded.
A memory leak and required reboot that occurred when using the StoreAll Windows Client to
write or create multiple small files has been fixed.
When performing a segment evacuation on a shadow directory (due to a bad segment), the
evacuation no longer fails.
Previously when hard links were created on a StoreAll file system from the StoreAll Windows
Client, unmounting the file system might result in a failure. The fix ensures the failure no longer
occurs.
The HP-SMB Srvsvc service no longer fails due to an excessive number of RPC connection
requests.
The file name length value was corrected in the Notify response packet to prevent the SMB client
from failing during create, change, or delete operations on files or folders.
Access-based enumeration now works for all types of directory enumeration requests for SMB
clients.
Previously, on the 9730 platform, it was possible that an event indicating, "The controller is not
responding. Reboot the server and replace controller if this does not resolve the issue." might be
sent even though there was not a real hardware or firmware issue with the controller. If HA was
enabled, this would trigger a failover of the owned segments to its partner blade and a reboot
of the blade. This false indication of failure has been resolved, so that a failover will only occur
when needed to recover from a hardware or firmware issue in the controller.
After archiving files, segment evacuation no longer fails and an RO lock error no longer occurs
when accessing files on another node.
Fixes in the 6.1.4 release
Directory change notification was not working for SMB1 clients.
Administrators were unable to add a user as nasxxx in CIFS Authentication.
Share administrators were unable to add users and groups with parenthesis and ampersands in
the name to a CIFS share.
The Windows IBRIX Client (WIC) would crash when WIC was built in debug mode.
A memory leak was occurring in Fusion Manager.
There were SAS topology issues, resulting from firmware flashes and simultaneous blade boots.
The var/log/message file was not getting rotated nightly.
Thousands of /tmp/tmp*.lvmtool directories were being created.
IBRIX nodes were not discoverable when the Fusion Manager IP was used in HP Systems Insight
Manager (SIM).
A crash would sometimes occur while renaming a folder.
Quotas were being incorrectly reported after an upgrade.
The IoLockFile FSD interface was crashing frequently (4 to 9 minutes intervals) because of an
assertion failure in file locking.
The ibrix_fsck command was showing "illegal inode number while reading inode."
The message LW_ERROR_INVALID_PARAMETER was appearing frequently in the logging.
Fixes 9