6.2.2 HP IBRIX 9000 Storage Release Notes (AW549-96061, January 2013)

IBRIX 9000 Windows clients
• Reading of snaps as memory mapped files is not supported. Undesired results can occur if a snap
file is used as memory mapped file while the current version of the file is being modified by a
different instance.
ibrix_fsck command
• The log files for user-initiated tasks (such as running ibrix_fsck and migrating or rebalancing
segments) are not rotated automatically. To control the space used by these log files, you will
need to maintain them manually. The log files are located in /usr/local/ibrix/log.
• After running a tiering, rebalance or segment evacuation job, a phase 1 of the ibrix_fsck
command might display a message regarding “bad replica” inodes. The following is an example
of the message from a phase 1 ibrix_fsck log:
Entry 'F000000060000FEAF.DAT' in
/.ibrixShadowRoot/s_1/g_367/i_100b335b7_edd68d01/D00000006000005FE
(11812038) has bad replica inode 17877133.
This message indicates that a replica inode was deleted from the file system by a user application,
but the directory entry (DENTRY) pointing to the replica has not been removed. There is not an
issue with the file system, and this situation does not impact file system operations. The DENTRY
that points to the deleted replica can be removed by running a phase 1 ibrix_fsck in corrective
mode. See the HP IBRIX 9000 Storage CLI Reference Guide for more information.
Windows Client
• If the IBRIX Windows Client is registered with Fusion Manager already, clicking on Start Service
After registration under the Registration tab displays a Response Code =400 error. Click the
Recover Registration option instead.
• When hard links are created on an IBRIX file system from the IBRIX Windows Client, the unmount
of the file system might result in a crash. Save the data and close the open files before performing
the unmount operation.
General
• The ibrix_pv -a -o mpath command does not recognize a multipath device. The command
works properly when an argument is added to ignore the standard SCSI devices. Execute the
command as follows, specifying the path to your device.
ibrix_pv -a -o accept:/dev/mapper/mpath10,~standard
• The ibrix_lv -d -s <range of Segments> command sometimes displays a “failed
command” message. Although the segments for which the command fails are still listed by the
ibrix_lv -l command, they are successfully removed from the underlying Operating System
LVM view. This issue is a timing condition for large file system delete operations where the delete
command times out while waiting for a response from the storage. Although the deletion was
successful the command reports it as failed and IBRIX preserves the associated volume group (ivg)
and logical volume (ilv). This issue has been observed on the HP IBRIX 9730.
To resolve this issue, rerun the logical volume delete command using the “-X” override option, for
example: ibrix_lv -d -s <ilv#> —X
The override option forces the removal of the IBRIX Logical Volume record from the IBRIX database.
• When using the ibrix_vs -a command during file system extension, the command fails on a
combined cluster configuration (such as 9730 and 9320) with the following error message:
Lun already set for physical volume dxx can two vendorstorages see the
same luns?
Workarounds 23