6.0.2 HP IBRIX X9000 Storage Release Notes (AW549-96044, January 2013)

Agile management console
The agile management console is now required on all file serving nodes. The management console is
active on one node and passive on the other nodes.
Spillover
Spilling over sequentially written files from one segment to another is disabled in the 6.0 release; no
new spillover chunks will be created. If a segment is full, writes to files in that segment will fail with
-ENOSPC (-28), even if there is space available in other segments. Existing spillover files generated
in the 5.x release will continue to work (read/write). Writes will continue to work if there is space
available in the segments to which the file belongs. If the segments are full, writes will fail with
–ENOSPC.
Existing spillover files cannot be snapped and cannot be moved into a snap tree.
To minimize out-of-space errors when creating files, it is important to ensure that segments are balanced.
If some segments are over 80% full and other segments are less than 80% full, it is advisable to run
a segment rebalance task.
Remote replication
The following changes have been made in this release:
• The remote replication commands have been renamed. Be sure to update any scripts using the
old names. Event messages still refer to remote replication as CFR.
◦ The ibrix_cfrjob command has been renamed ibrix_crr. The new -X option specifies
an exported directory on the target and is used only for remote cluster replication. Previously,
-P was used for this purpose. The -P option is now used to specify an arbitrary target
directory and applies to both same cluster and remote cluster replication.
◦ The ibrix_export_cfr command has been renamed ibrix_crr_export. There are
no other changes.
◦ The ibrix_exportcfrpreference command has been renamed ibrix_crr_nic.
Export preferences are now referred to as server assignments.
• The GUI has been modified to simplify starting replication and to simplify selecting and modifying
server and NIC assignments for remote replication exports.
• CRR now supports Run-Once replication of a file system snapshot. The GUI must be used for this
feature.
• CRR now supports specifying an optional target directory. For same-cluster replications, the target
directory is a subdirectory under the target file system. For remote replications, the target directory
is either a subdirectory under the target file system or a subdirectory under the target file system
and exported directory.
• When you specify a source directory for a Run-Once replication (using the ibrix_crr –S
option) , the files under the source directory are replicated without replicating the source directory
path. The root of the replica on the target is based strictly on the configured target file system,
the configured target exported directory (remote cluster only), and the optional target directory.
Examples:
Source directory: /srcFS/a/b/c
nl
Exported file system and exported directory on the target: /destFS/1/2/3
You can configure a replication that does not include an additional target directory. The replication
command is:
ibrix_crr –s –o –f srFs –S a/b/c –C tcluster –F destFs –X 1/2/3
The contents of /srcFS/a/b/c is replicated to destFs/1/2/3/{contents_under_c}.
When the command includes the -P option to specify the target directory a/b/c:
6 New features