6.0 HP X9000 File Serving Software File System User Guide (TA768-96043, October 2011)

Cannot mount on an X9000 client
Verify the following:
• The file system is mounted and functioning on the file serving nodes.
• The mountpoint exists on the X9000 client. If not, create the mountpoint locally on the client.
• Software management services have been started on the X9000 client (see “Starting and
stopping processes” in the administrator guide for your system).
NFS clients cannot access an exported file system
An exported file system has been unmounted from one or more file serving nodes, causing X9000
Software to automatically disable NFS on those servers. Fix the issue causing the unmount and
then remount the file system.
User quota usage data is not being updated
Restart the quota monitor service to force a read of all quota usage data and update usage counts
to the file serving nodes in your cluster. Use the following command:
ibrix_qm restart
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 <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
host_name ...................... ib50-87 <-- Verify owner of segment
42 Maintaining file systems