6.2.1 HP IBRIX 9000 Storage Release Notes (TA768-96074, December 2012)

The following restrictions apply to both hybrid file systems and pure 6.x file systems:
• A snap tree root cannot be renamed. Also, the path to a snap tree root cannot be changed.
• Rename is allowed when neither the old directory or the new directory are in snap trees.
• Rename is allowed when the old directory and the new directory are in the same snap tree.
Rename is not allowed when the directories are in different snap trees.
These restrictions are intended to prevent hybrid snap trees containing files with the old format. However,
hybrid snap trees can still occur when a directory having the new format is populated, using rename,
with old format objects and that directory is then made into a snap tree root or is renamed into a snap
tree. The IBRIX 9000 software does not prevent this situation because it could take a prohibitively long
amount of time to perform a complete scan for old objects in the sub tree being moved if the new sub
tree was sufficiently large.
Fixes
This section provides information about the fixes that were made in the 6.2.1 release.
• 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 IBRIX 9000 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 IBRIX system for maintenance
reasons, the segment server hosting the root segment took 30 minutes per NFS export to timeout
and finally unmount.
• When accessing IBRIX 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
Fixes 7