5.5.4 HP X9000 Series Release Notes (TA768-96054, September 2011)

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

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.

Cluster component states

• Changes in file serving node status do not appear on the management console until 6 minutes

after an event. During this time, the node status may appear to be UP when it is actually DOWN

or UNKNOWN. Be sure to allow enough time for the management console to be updated before

verifying node status.

• Generally, when a vendorstorage component is marked Stale, the component has failed

and is not responding to monitoring. However, if all components are marked Stale, this implies

a failure of the monitoring subsystem. Temporary failures of this system can cause all monitored

components to toggle from Up, to Stale, and back to Up. Common causes of failures in the

monitoring system include:

◦ Reboot of a file-serving node

◦ Network connectivity issues between the management console and a file serving node

◦ Resource exhaustion on a file serving node (CPU, RAM, I/O or network bandwidth)

While network connectivity and resource exhaustion issues should be investigated, they can occur

normally due to heavy workloads. In these cases, you can reduce the frequency at which

vendorstorage components are monitored by using the the following command:

ibrix_fm_tune -S -o vendorStorageHardwareStaleInterval=1800

The default value of this command is 900; the value is in seconds. A higher value reduces the

probably of all components toggling from Up to Stale and back to Up because of the conditions

listed above, but will increase the time before an actual component failure is reported.

14 Fixes