NFS problems

Client's inability to mount directories indicates NFS problems

NFS problems are indicated when the filer and the client can communicate with each other using the ping command and the client can connect to the filer using telnet, but the client cannot mount volumes or directories from the filer.

How to troubleshoot NFS problems

Complete the steps in the following table to troubleshoot NFS problems.

Step Action
1 Make sure that the filer is licensed for NFS by entering the license command at the filer prompt. If the following message appears 
nfs not licensed
or if a message with protocols other than NFS appears but NFS is absent, you must get a license for NFS.

Note: For information about how to get a license, contact Network Appliance Technical Support, as described in "Getting technical assistance."

2 Make sure that the filer can correctly look up the client host name.
3 Make sure that NFS service has been turned On using the nfs on command.
4 Make sure that the filer and the client are using correct IP addresses and names.
5 Sometimes a client can see the filer but gets a Permission Denied message when requesting a mount. If this happens, follow these steps:
  • Make sure that you defined the file systems correctly in the filer's /etc/exports file on the root volume and that you ran the exportfs command on the filer.
  • On certain clients, the mount request does not come from the root user using a privileged port. The filer denies such mount requests by default to ensure secure access. To grant such mount requests, enter the following options command: 
    options nfs.mount.rootonly off

    To make this change permanent, add the preceding command to your /etc/rc file on the root volume.

Copyright © 1999, Network Appliance, Inc. All rights reserved.

Part No. 210-02334
File: trbl18.htm
Last updated: 02/24/99 12:17:24