6.3 HP StoreAll Storage Release Notes (TA768-96086, April 2013)

• A crash would sometimes occur while renaming a folder.
• Quotas were being incorrectly reported after an upgrade.
• The ibrix_fsck command was showing "illegal inode number while reading inode."
• The ibrix_vs -a command would fail on combined 9730+9720 and 9320+9730 clusters.
• Long delays (approximately 10 minutes) followed by an HTTP status code in the 5XX range would
occur while using the StoreAll REST API.
• The server running the active Fusion Manager would inexplicably reboot.
• Online upgrades no longer requires a user virtual interface (VIF).
• The Firmware Management Tool no longer displays a Could not recommend any flash
action... message after an upgrade.
• Previously when hard links were created on a StoreAll file system from the StoreAll Windows
Client, the unmount of the file system might result in a crash. The fix ensures the crash no longer
occurs.
• The automated offline upgrade can now handle clusters with more than 10 nodes.
• The 10Gb NIC driver is updated during the StoreAll v6.2.X software upgrade. However, the new
driver was not utilized/loaded until after the server has been rebooted. If you run the upgrade
firmware tool (hpsp_fmt) before you reboot the server, the tool detects that the old driver was
still being used.
• After an upgrade, the following message no longer appears:
The IbrixArchiving rpm is not installed.
• Use of StoreAll Native clients for any SUSE or SLES kernel is now supported for file systems with
Express Query enabled.
• Long delays (approximately 10 minutes) followed by an HTTP status code in the 5XX range would
occur while using the StoreAll REST API.
• The MDImport tool can now import large files created by MDExport or ibrix_audit_reports.
• Actively running tasks (Fusion Manager event-based) were stopping the reporting status to the
active Fusion Manager (FM) if an FM restart occurred on the system doing the monitoring for that
task.
• Unable to disable antivirus on a file system when tasks other than avscan (such as migrator,
rebalance, and evacuator) were running on the file system. The issue has been resolved so that
you cannot disable antivirus when only the avscan task is running on the file system.
• The add/remove scan engine command would fail with an RC:5 and RC:17 error during the
removal or addition of a virtual scan engine, usually when these commands were attempted while
multiple scans were in progress.
• Fixed issues seen when on-access and avscan were accessing the same file at the same time.
Certain scenarios with onacess scans running in parallel with an avscan task were causing
the reads triggered by onaccess scans to timeout with a "Resource unavailable error." The issue
was seen when the avscan task was run on a large file, while an onaccess scan for the same
file was already in progress.
• Quarantine utility operations (such as list, reset, delete, and move) of infected files with a total
path length exceeding 200 characters caused the quarantine utility and the corresponding utility
operation on the file to stop working. Memory is now dynamically allocated based on the path
length of the infected file.
• If you set the antivirus scan policy to CLOSED, the antivirus scan in a few instances would not
detect an infected file on the CIFS client; however, if you selected the BOTH antivirus scan policy,
the scan would detect and quarantine the infected file when the file was opened. A 35–second
6 Fixes in the 6.3 release