5.5.5 HP IBRIX X9000 Release Notes

Failover
• An informational message was needed for failback operations requiring the administrator to run
the ibrix_pv -a command.
• NICs were not failed over in parallel when a server was powered down.
Other operations
• When a server did not respond because it was rebooting, the error message Err: New inode's
required delegation is missing was displayed.
• The support ticket feature did not collect the /usr/local/ibrix/log/daily directory.
• The Linux SLES10u3 client did not start properly.
• In certain situations (such as the failure of a disk in shared storage), a runaway process could
cause all X9720 vendorstorage objects to be marked Stale. The server eventually rebooted and
the vendorstorage objects returned to normal operations.
• Changes in the health status of segments and the underlying LUNs were not reported.
• Numerous error messages were reported when a disk failed.
• The message ibrix_journal_healme(): Err: Ignore request with inode inum=0
was issued repeatedly.
• The get_seg command did not display filenames with special characters correctly.
• A file serving node failed during a snapshot operation.
Workarounds
Following are workarounds for product situations that may occur:
X9000 upgrades
When a cluster is configured with a dedicated, standard management console, the Quick Restore
installation procedure installs both the IbrixFusionManager and the IbrixServer packages on the
dedicated, standard management console and on each node of the cluster, which eventually causes
the upgrade to fail. To avoid the failure, uninstall the IbrixServer package from the dedicated, standard
management console, and uninstall the IbrixFusionManager package from the file serving nodes. You
can then upgrade the cluster.
IMPORTANT: This workaround does not apply to clusters using the agile management console. The
RPMs should not be uninstalled on these clusters.
Complete the following steps:
1. On the standard management console, check for the IbrixServer RPM:
# rpm –qa | grep –i IbrixServer
If the RPM is present, the output will be similar to the following:
IbrixServer-<version>
2. If the IbrixServer RPM is present, uninstall the RPM:
# rpm -e IbrixServer-<version>
3. On each file serving node, check for the Ibrix Fusion Manager RPM:
# rpm –qa | grep –i IbrixFusionManager
If the RPM is present, the output will be similar to the following:
Fixes 9