6.2.3 HP StoreAll Storage Release Notes (update)

• 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+X9720 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.
Fixes in the 6.2.1 release
• There is no longer a 100 LUN limit when creating a file system.
• When a blade was pulled out, the segment server might not failover.
• The summary page does not show relevant message of the action taken by the user. The UI has
since been modified.
• Request for a method for setting the pasv_address parameter in the vsftpd.conf file. This
parameter can now be set as follows:
◦ CLI. Enter the following command, which will write the pasv_address parameter
(pasv_promiscuous=YES) into the sftpd configuration file:
ibrix_ftpshare -m ftp_share1 -c profile1 -I 10.9.60.61:21 -S
"allow_nat=true"
◦ GUI. A new field named Allow NAT connections has been added to the FTP share modification
window.
• Fusion Manager (FM) restarted a CFR job even if it is marked “stopped by the user.” Fusion
Manager has been modified so that it does not automatically restart a CFR job when the user
requests the CFR job to be stopped.
• A soft lockup of the CPU was occurring during connection/delegation recovery.
• The creation of directory tree quota names with a colon (:) in the name produced undesirable
results and it further impacted the creation of new "normal" directory tree quota names until the
entry with the colon character was removed. Users are now told in the HP StoreAll Storage File
System User Guide that they cannot create a directory tree quota containing a comma (,) or colon
(:) character.
• When performing a "graceful" shutdown (ibrix_umount) of the StoreAll system for maintenance
reasons, the segment server hosting the root segment took 30 minutes per NFS export to timeout
and finally unmount.
• When accessing StoreAll file systems through NFS, the client NFS access would hang intermittently.
• When segments reached 70–80% of capacity, clients were unable to write to an SMB share.
• The quota current size would be reduced after running the rebalance task, even though files were
not modified or deleted. During movement of files across segments, there are intermediate replica
files that are created. Once data from an original file is synced with its replica, the original file
is deleted and the replica is promoted as the original file. These replicas have to be marked with
the directory quota ID, which is the same as that of the original master file. That was not occurring.
As the original file was deleted post replication, the directory quota accounted for it was getting
decremented. Since the newly created file was not marked with the directory quota ID, it was
never was accounted for. As a result, a reduction in quota usage was shown post replication.
The fix was to mark the replica created with the quota ID same as that of the original file, so any
data written into this file is accounted for against the set quota ID.
• Data tiering could result in zero length files.
Fixes 11