6.5 HP StoreAll OS User Guide

1. Identify the file serving node that owns the segment. This information is reported on the
Filesystem Segments panel on the Management Console.
2. Run phase 0 and phase 1 of the ibrix_fsck command to verify the issue with the segment.
You can run the command on the file system or specify the segment name using the –s LVNAME
parameter:
ibrix_fsck -p 0 -f FSNAME [-s LVNAME] [-c]
ibrix_fsck -p 1 -f FSNAME [-s LVNAME] [-c]
3. If you have set Fusion Manager to fail over when a segment becomes unavailable, failover
occurs automatically. For more information, see the ibrix_fm_tune command in the HP
StoreAll Command Line Reference Guide. You can manually fail over the file serving node.
See the administration guide for your system for more information about this procedure.
4. If you have set Fusion Manager to make the segment available after failover, the segment
automatically becomes available after failover. For more information, see the ibrix_fm_tune
command in the HP StoreAll Command Line Reference Guide. To manually make the segment
available:
a. Enter the following command to clear the in_fsck flag:
ibrix_fsck -f FSNAME -C
b. Enter the following command to clear the unavailable flag on the specified segment and
file system:
ibrix_fsck -f FSNAME -C -s LVNAME
c. When following message displays, enter yes to continue:
Warning: Clearing UNAVAILABLE/RO Flag on a Segment can result in
further damage to your filesystem. Type 'yes' to continue :
d. If the segment is still not available, contact HP Support.
5. Fail over the file serving node to its standby.
6. Reboot the file serving node.
7. When the file serving node is up, verify that the segment, or LUN, is available.
If the segment is still not available, contact HP Support.
SegmentRejected is reported
This alert is generated by a client call for a segment that is no longer accessible by the segment
owner or file serving node specified in the client's segment map. The alert is logged to the a
StoreAll.log and messages files. It is usually an indication of an out-of-date or stale segment
map for the affected file system and is caused by a network condition. Other possible causes are
rebooting the node, unmounting the file system on the node, segment migrations, and, in a failover
scenario, an unresponsive kernel, or a network RPC condition.
To troubleshoot this alert, check network connectivity among the nodes, ensuring that the network
is optimal and any recent network conditions have been resolved. From the file system perspective,
verify segment maps by comparing the file system generation numbers and the ownership for those
segments being rejected by the clients.
Use the following commands to compare the file system generation number on the local file serving
nodes and the clients logging the error.
/usr/local/ibrix/bin/rtool enumseg <FSNAME> <SEGNUMBER>
For example:
rtool enumseg ibfs1 3
segnum=3 of 4 -----------
fsid ........................... 7b3ea891-5518-4a5e-9b08-daf9f9f4c027
fsname ......................... ibfs1
device_name .................... /dev/ivg3/ilv3
host_id ........................ 1e9e3a6e-74e4-4509-a843-c0abb6fec3a6
Troubleshooting file systems 55