Identifying NFS problems

If you are encountering NFS problems, follow these steps.

If a client is having NFS trouble, do the following:

  1. Verify that the network connections are good.
  2. Verify that the inetd, portmap, and biod daemons are running on the client, by following the instructions in Getting the current status of the NFS daemons.
  3. Verify that a valid mount point exists for the file system being mounted.
    For more information, see Configuring an NFS client.
  4. Verify that the server is up and running by running the following command at the shell prompt of the client:
    /usr/bin/rpcinfo  -p  server_name
    If the server is up, a list of programs, versions, protocols, and port numbers is printed, similar to the following:
    program    vers  proto      port
    100000        2      tcp       111    portmapper
    100000        2      udp       111    portmapper
    100005        1      udp      1025    mountd
    100001        1      udp      1030    rstatd
    100001        2      udp      1030    rstatd
    100001        3      udp      1030    rstatd
    100002        1      udp      1036    rusersd
    100002        2      udp      1036    rusersd
    100008        1      udp      1040    walld
    100012        1      udp      1043    sprayd
    100005        1      tcp       694    mountd
    100003        2      udp      2049    nfs
    100024        1      udp       713    status
    100024        1      tcp       715    status
    100021        1      tcp       716    nlockmgr
    100021        1      udp       718    nlockmgr
    100021        3      tcp       721    nlockmgr
    100021        3      udp       723    nlockmgr
    100020        1      udp       726    llockmgr
    100020        1      tcp       728    llockmgr
    100021        2      tcp       731    nlockmgr
    If a similar response is not returned, log in to the server at the server console and check the status of the inetd daemon by following the instructions in Getting the current status of the NFS daemons.
  5. Verify that the mountd, portmap and nfsd daemons are running on the NFS server by entering the following commands at the client shell prompt:
    /usr/bin/rpcinfo  -u  server_name  mount
    /usr/bin/rpcinfo  -u  server_name  portmap
    /usr/bin/rpcinfo  -u  server_name  nfs
    If the daemons are running at the server, the following responses are returned:
    program  100005  version  1  ready  and  waiting
    program  100000  version  2  ready  and  waiting
    program  100003  version  2  ready  and  waiting
    The program numbers correspond to the commands, respectively, as shown in the previous example. If a similar response is not returned, log in to the server at the server console and check the status of the daemons by following the instructions in Getting the current status of the NFS daemons.
  6. Verify that the /etc/exports file on the server lists the name of the file system that the client wants to mount and that the file system is exported. Do this by entering the command:
    showmount -e server_name
    This command lists all the file systems currently exported by the server_name.
  7. For NFS version 4, verify that the NFSv4 domain is properly set.
  8. For NFS version 4, verify that the nfsrgyd daemon is running.
  9. If you are using enhanced security, see RPCSEC-GSS problem determination.