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

• Running replication with antivirus scanning no longer corrupts ibrmode, which previously made
the scan appear not to occur.
• 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 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.
• The HP-SMB Srvsvc service no longer fails due to an excessive number of RPC connection
requests.
• Access-based enumeration now works for all types of directory enumeration requests for SMB
clients.
• After an upgrade on the StoreAll 9730, a simultaneous reboot of multiple servers could cause
the SAS expanders in MDS600 and D6000 disk enclosures to remain undiscovered. This resulted
in the hard disk drives not appearing and the disk enclosure failing to come online, even in a
degraded mode. This has been corrected with an upgrade to Virtual SAS Manager firmware
version 3.2.2.0.
• After archiving files, segment evacuation no longer fails and an RO lock error no longer occurs
when accessing files on another node.
• Significantly improved sequential read performance for HP-SMB (up to four times faster compared
to previous releases).
• The HP-SMB service called lwiod would restart due to an assertion failure, which occurred when
a client attempted to recover a previously opened session after a disconnect/connect failure.
• The HP-SMB share management utility called lwnet previously failed when run with the lwnet
share --set-info option. This occurred only when a domain user was used in the command,
and the node had been removed from the domain.
• The HP-SMB service lwio failed when multiple clients accessed files or folders under a share and
simultaneously an application like PowerShell subscribed to event notifications on a shared folder.
• When using the ibrix_avquarantine command, if the complete path length for the infected
file exceeded 200 characters, a crash occurred and the infected file was not moved.
• Fixed the order of components during an upgrade so that creating archiving-enabled file systems
post-upgrade no longer requires a restart of the Fusion Manager component.
• LUN discovery was corrected to handle multiple comma-delimited vendor storage names.
• Fixed an issue that caused i_blocks and i_total_blocks to become out of sync when a directory
was being created.
• Refresh stale dentry now displays when a misidentified dangler or a legitimate corrupted
directory condition occurs.
• A missing attribute in the LDAP server user record now generates an error in the log, but no longer
results in a crash.
• Wrapper scripts were modified to accept spaces in arguments.
• The IBFS driver registry entry is now stored in memory to avoid the overhead of reading from the
registry.
• Fusion Manager correctly redirects stdout and stderr messages to the log file, which ensures
that phases 2 and 3 of the ibrix_fsck command will complete.
• The file name in the DCN response was changed to be the relative Windows file name (which is
the Windows server behavior) instead of the absolute UNIX file name.
10 Fixes