6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

restrictions have been implemented on rename operations. The following restrictions apply to hybrid
file systems:
• Only directories created in version 6.0 or later can become snap tree roots.
• If the old directory is not in a snap tree and the new directory is in a snap tree, rename is allowed
only if the object being renamed is snapable (that is, it has the new inode format).
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
Fixes in the 6.2.2 release
• Administrators were unable to add a user as “nasxxx” in SMB Authentication.
• Share administrators were unable to add users and groups with parenthesis and ampersands in
their name to an SMB share.
• 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 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.
Fixes 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.
Fixes 7