6.3.3 HP StoreAll OS Release Notes (AW549-96082, January 2014)

ibrix_fsck
• 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 StoreAll Storage CLI Reference Guide for more information.
Installation and network configuration
• During the installation process, the user is prompted to configure an NTP server for time
synchronization. However, when a cluster node is joined to an Active Directory (AD) domain later
in the process, the HP-SMB authentication service attempts to synchronize the time with the AD
server. If the NTP and AD servers are not in sync, this causes the cluster nodes to receive conflicting
time updates, which can lead to errors such as file system creation failures.
To avoid this issue, ensure the AD server and the NTP server are synchronized so they have the
same time. Or, ensure that the AD server and the StoreAll cluster are configured to synchronize
the time from the same NTP server.
• After an upgrade or a new installation, the default value for the
clearSegmentUnavailableUponFailover parameter of the ibrix_fm_tune command
is incorrectly set to false (the correct default is true). To resolve this issue, run the following command
to reset the default value to true:
ibrix_fm_tune –S –o clearSegmentUnavailableUponFailover=true
• Setting a standby NIC for a user VLAN parent device results in a FAILED status when executing
the ibrix_haconfig -l command.
To avoid the FAILED status when configuring VLAN user NICs with standby NICs, create a parent
device (for example, bond0.vlan) with two VIF devices: bond0.vlan:2 and bond0.vlan:3.
In this instance, bond0.vlan:2 is the user NIC IP and bond0.vlan:3 is the standby VIF.
• On X9720 systems with G6 blades, the Quick Restore installation reports that the G6 Ethernet
firmware must be upgraded. The Ethernet device (eth0) must be up when you upgrade the
firmware. Use the following command to bring up eth0 and then upgrade the firmware:
# ifup eth0
The following document provides additional detail for HP Support personnel:
http://saw.cce.hp.com/km/saw/view.do?docId=emr_na-c03466768
• When creating a user NIC with a VLAN tag on a bond, running the ibrix_nic -c command
causes the parent bond to become degraded. The workaround is to determine the device that is
down and then bring up that device manually. For example, if bond0 is made up of eth4 and
eth5, use ifconfig to determine which device is down. Then use ifup to bring up the device,
such as ifup eth4.
Workarounds 25