6.3.2 HP StoreAll OS Release Notes

Documentation changes and additions
Modifying the /etc/hosts file on every StoreAll node is no longer necessary
The post upgrade steps in the 6.3 HP StoreAll Storage Administrator Guides (dated March 2013)
recommend that you modify the /etc/hosts file on every StoreAll node. This step was necessary in
an earlier release, but it is no longer necessary for 6.3.
Revision of text for creating a retention/WORM/auto-commit feature set
The 6.3 HP StoreAll Storage CLI Reference Guide tells you to use the ibrix_fs -c -f
<file_system_name> -p PVLIST -a -o retenDefPeriod=0 command for creating a file
system without the rentention/WORM/auto-commit feature. This command actually enables retention
with the retenDefPeriod set to zero and the defaults for all the other retention options.
If you do not want to use the retention/WORM/auto-commit feature, create the file system without
adding any of the retention -o options (retenMode, retenDefPeriod, retenMinPeriod,
retenMaxPeriod, or retenAutoCommitPeriod).
The file system does not need to be unmounted when Express Query settings are
enabled on a file system
The 6.3 HP StoreAll Storage CLI Reference Guide says that the file system must be unmounted while
running the ibrix_fs -T -E -f FSNAME command to enable Express Query settings on a file
system. The file system does not need to be unmounted to run the command.
Permissions cannot be assigned to objects individually for object mode shares
The “Creating StoreAll REST API shares” section in the 6.3 HP StoreAll Storage User Guide says that
objects (files) are always created with permissions 0700. Permissions cannot be assigned to objects
individually. Access to a container’s objects by other users is controlled at the container level.
Attribute names and value requirements
The “Upload custom metadata” section in the 6.3 HP StoreAll Storage User Guide says that the attribute
name and value must each have less than 80 characters in length when in reality the attribute name
and value must each have 80 characters or less in length.
Object mode API
In the "Best practices for HTTP REST API shares" section in the HP StoreAll Storage File System User
Guide, the text about putting object mode shares on retention-enabled file systems incorrectly mentions
the auto-commit feature. The correct text is:
Avoid putting object mode shares on retention-enabled file systems. The object mode API does not
include retention management features. Managing WORM or retention states must be performed
outside the API as described in the “Managing data retention” section.
In the "Object mode shares and data retention" section of the User Guide, references to the auto-commit
feature are incorrect. The correct text is:
If you choose to put an object mode API share on a retention-enabled file system, there are a few
differences in how WORM and retention operate for object mode shares. Auto-commit is disabled.
Files can be manually set to WORM by clearing all write permission bits, but files cannot be retained.
A WORM object cannot be modified nor replaced via the API, but it can be deleted since retention
is disabled.
Understanding how autocommit and data retention works
Depending on the defined autocommit and retention periods, it is possible that some files may not be
retained or a file may have a reduced retention period. Although a time period is set for autocommit
Documentation changes and additions 29