5.5.265 HP StorageWorks X9000 Series Release Notes

Remote replication
• Running the X9000 Software snapshot feature on a file system that was a replica target for
continuous remote replication could result in snapshot errors if the target was the root of the file
system.
• Subsequent remote replication jobs (run-once or continuous) started on the same source file system
to the same target file system did not sync all objects that were deleted on the source between
replications.
• Rapid combinations of creates, deletes, or renames using the same file names sometimes were
not replicated correctly.
• Running two or more replication tasks that were replicating to different subdirectories of the same
target cluster and file system did not always work well in previous releases if any of the parallel
replication tasks were Continuous.
Quotas
• When quotas were checked on a file system, errors were reported for file serving nodes that had
not mounted the file system.
• Server operations slowed when users exceeded their quotas.
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
6 Fixes