HP StoreAll Storage - Manual (Page 45)

File system alert is displayed after a segment is evacuated
When a segment is successfully evacuated, a segment unavailable alert is displayed in the GUI
and attempts to mount the file system will fail. There are several options at this point:
•
Mark the evacuated segment as bad (retired), using the following command. The file system
state changes to okay and the file system can now be mounted. However, the operation
marking the segment as bad cannot be reversed.
ibrix_fs -B -f FSNAME {-n RETIRED_SEGNUMLIST | -s RETIRED_LVLIST}
•
Keep the evacuated segment in the file system. Take one of the following steps to enable
mounting the file system:
◦ Use the force option (-X) when mounting the file system:
ibrix_mount –f myFilesystem –m /myMountpoint –X
◦ Clear the “unavailable segment” flag on the file system with the ibrix_fsck command
and then mount the file system normally:
ibrix_fsck -f FSNAME -C -s LVNAME_OF_EVACUATED_SEG
SegmentNotAvailable is reported
When writes to a segment do not succeed, the segment status may change to
SegmentNotAvailable
on the GUI and an alert message may be generated. To correct this
situation, take the following steps:
1. Identify the file serving node that owns the segment. This information is reported on the
Filesystem Segments panel on the GUI.
2. Fail over the file serving node to its standby. See the administration guide for your system for
more information about this procedure.
3. Reboot the file serving node.
4. 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 Iad.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, stale IAD,
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
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
host_name ...................... ib50-87 <-- Verify owner of segment
ref_counter .................... 1038
Troubleshooting file systems 45