HP StoreAll OS 6.5.1 Release Notes

Contact HP Support for assistance.
• If the ibrix_auth command fails after a QR restore of a server in a cluster with a message
similar to:
ibrix_auth -n IBRQA1.HP.COM -A [e-mail] -P password
-h hostnameX
Iad error on host hostnameX failed command (<HIDDEN_COMMAND>) status
(1) output: (Joining to AD Domain:IBRQA1.HP.COM With Computer DNS Name:
hostsnameX.ibrqa1.hp.com )
Verify the contents of the /etc/resolv.conf file is not empty. If it is empty, copy the contents
of the /etc/resolv.conf file on another server to the empty resolv.conf file.
Cluster component states
• Changes in node status do not appear on the management console until 6 minutes after an event.
During this time, the node status may appear to be UP when it is actually DOWN or UNKNOWN.
Be sure to allow enough time for the management console to be updated before verifying node
status.
• Generally, when a vendorstorage component is marked Stale, the component has failed
and is not responding to monitoring. However, if all components are marked Stale, this implies
a failure of the monitoring subsystem. Temporary failures of this system can cause all monitored
components to toggle from Up, to Stale, and back to Up. Common causes of failures in the
monitoring system include:
◦ Reboot of a node
◦ Network connectivity issues between the management console and a file serving node
◦ Resource exhaustion on a file serving node (CPU, RAM, I/O or network bandwidth)
While network connectivity and resource exhaustion issues should be investigated, they can occur
normally due to heavy workloads. In these cases, you can reduce the frequency at which
vendorstorage components are monitored by using the following command:
ibrix_fm_tune -S -o vendorStorageHardwareStaleInterval=1800
The default value of this command is 900; the value is in seconds. A higher value reduces the
probability of all components toggling from Up to Stale and back to Up because of the conditions
listed above, but will increase the time before an actual component failure is reported.
Data retention and validation
• When you use the ibrix_datavalidation -s -f FSNAME [-d PATH] command, keep
in mind that if the PATH is a StoreAll Archiving Infrastructure Directory (.archiving, .snapshot,
.snapmgmt, .audit, etc.), the files under them will not be validated.
• The ibrix_vs_snap command cannot delete a block snapshot file system that is enabled for
data retention. Instead, use the ibrix_fs command with the -R option. For example:
ibrix_fs -d -f block_snap_ifs2_1 -R
• Directories are not supported in the path list for the ibrix_reten_adm command. However,
the command does not display the correct error message when the path list includes a directory.
• The ibrix_reten_adm -e command fails for WORM files that are not retained. If a WORM
file is not retained (either it has never been retained, or it was retained but its retention period
has expired), use the touch command to set its last accessed time (atime) forward to the desired
expiration time. The file will then be retained until that time.
14 Workarounds