6.3.2 HP StoreAll OS Release Notes

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 StoreAll Storage CLI Reference Guide for more information.
Windows Client
• If the StoreAll 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.
General
• Obtaining a crash dump on an X9720 with ProLiant G6 servers may occasionally be unsuccessful.
The X9720 platform use two bond devices and the crash kernel attempts to use both bond devices,
but an error in the NIC driver results in a failure when starting the second bond. To work around
this issue, you can disable bond0 as follows:
1. In the following files, change ONBOOT=yes to ONBOOT=no:
- /etc/sysconfig/network-scripts/ifcfg-bond0
- /etc/sysconfig/network-scripts/ifcfg-eth0
- /etc/sysconfig/network-scripts/ifcfg-eth3
2. Enter the following command:
touch /etc/kdump.conf
3. Enter the following command:
/etc/init.d/kdump restart
Once the crash dump is created, you can re-edit these files and change the setting back to
ONBOOT=yes.
• A crash might occur if there is a change in ownership of the file while a quota is being enabled.
There are plans to provide a fix in a future release.
• The output from the ibdircheck command might show incorrect statistics counters. For some
conditions the number of errors does not match the number of corrections. There are plans to fix
this issue in a subsequent patch. If you encounter this issue, contact HP support for analysis of the
ibdircheck logs to determine if you have a benign situation or if you have any file system errors
truly left uncorrected.
• After the files are archived, evacuation might fail and you might see an RO lock error message
when you attempt to access the files from the second node.
To resolve this issue:
1. Unload the CommVault driver from all nodes on hosts that control segments for this file system.
26 Workarounds