6.0.1 HP IBRIX X9000 Release Notes

ID>-<FS-ID>.info (for example, Rebalance_29-ibfs1.info). Following is an example
of the log file:
070390:0518545 | <INFO> | 3075611536 | collect counters from segment 3
070391:0520272 | <INFO> | 3075611536 | segment 3 not migrated chunks 1
<this line shows the segment has 1 chunk>
070391:0520285 | <INFO> | 3075611536 | segment 3 not migrated replicas 0 070391:
0520290 | <INFO> | 3075611536 | segment 3 not migrated files 0
070391:0520294 | <INFO> | 3075611536 | segment 3 not migrated directories 0
070391:0520298 | <INFO> | 3075611536 | segment 3 not migrated root 0
070391:0520302 | <INFO> | 3075611536 | segment 3 chunk: inode inum 300000017
(29B3A23C), poid hi64 300000017 (29B3A23C), primary 500000017 <this line
shows information about the chunk>
Run the inum2name command to identify the symbolic name of the chunk file:
root@centos bin]# ./inum2name --fsname=ibfs 500000017
ibfs:/sliced_dir/file3.bin
After obtaining the name of the file, use a command such as cp to move the file manually. Then
run the segment evacuation process again.
NDMP
• When Symantec NetBackup is used, a full backup job fails for a file system with large directory
tree. To correct this, set TYPE=tar in the Backup Selections tab in Symantec NetBackup. This
changes the backup type to tar instead of the default dump and forces NetBackup to handle the
file-based NDMP file history.
Ibrix Collect
• If collection does not start after a node recovers from a system crash, check the /var/crash/
<timestamp> directory to determine whether the vmcore is complete. Ibrix Collect does not
process incomplete vmcores. Also check /usr/local/ibrix/log/ibrixcollect/
kdumpcollect.log for any errors.
• If the status of a collection is Partially_collected, typically the management console service
was not running or there was not enough space available in the /local disk partition on the
node where the collection failed. To determine the exact cause of a failure during collection, see
the following logs:
◦ /usr/local/ibrix/log/fusionserver.log
◦ /usr/local/ibrix/log/ibrixcollect/ibrixcollect.py.log
• Email notifications do not include information about failed attempts to collect the cluster
configuration.
• In some situations, ibrix_collect successfully collects information after a system crash but
fails to report a completed collection. The information is available in the /local/ibrixcollect/
archive directory on one of the file serving nodes.
Migration to an agile management console configuration
When a cluster is configured with a dedicated, standard management console, the Quick Restore
installation procedure installs both the Fusion Manager and the File Serving Node packages on the
dedicated, standard management console and on each node of the cluster. If you then attempt to
migrate to an agile management console configuration, the migration procedure will fail. To avoid
the failure, uninstall the Ibrix Server package from the dedicated, standard management console, and
uninstall the Ibrix Fusion Manager package from the file serving nodes. You can then perform the
migration.
Complete the following steps:
Workarounds 13