NFS挂载问题汇总

1.  The rpcbind failure Error. The following example shows the message that appears on the client system during the boot process or in response to an explicit mount request:
   • nfs mount: server1:: RPC: Rpcbind failure
     RPC: Timed Out
     nfs mount: retrying: /mntpoint

The error in accessing the server is due to:

1. • The combination of an incorrect Internet address and a correct host or node name in the hosts database file supporting the client node.
   • The hosts database file that supports the client has the correct server node, but the server node temporarily stops due to an overload.

To solve the rpcbind failure error condition when the servernode is operational, determine if the server is out of critical resources (forexample, memory, swap, or disk space).

2. The server not responding Error The following message appears during the boot process or in response to an explicit mount request, and this message indicates a known server that is inaccessible.

NFS server server2 not responding, still trying

 Possible causes for the server not respondingerror are:

2. • The network between the local system and the server is down. To verify that the network is down, enter the ping command (ping server2).
   •  The server ( server2) is down.
      

 3The NFSclient fails a reboot Error. If you attempt to boot an NFS client andthe client-node stops, waits, and echoes the following message:

Setting default interface for multicast: add net 224.0.0.0: gateway:
client_node_name.

these symptoms might indicate that a client isrequesting an NFS mount using an entry in the /etc/vfstab file, specifying a foreground mount from anon-operational NFS server.

To solve this error, complete the following steps:

1. To interrupt the failed client node pressStop-A, and boot the client into single-user mode.

2. Edit the /etc/vfstab file to comment out the NFSmounts.

3. To continue booting to the default run level(normally run level 3), press Control-D.

4. Determine if all the NFS servers are operationaland functioning properly.

5. After you resolve problems with the NFS servers,remove the comments from the /etc/vfstab file.

Note – If the NFS server is not available, an alternative to commenting out
the entry in the /etc/vfstab file is to use the bg mount option so that the
boot sequence can proceed in parallel with the attempt to perform the NFSmount.
 

4. The service not responding Error.  The following message appears during the boot process or in response to an explicit mount request, and indicates that an accessible server is not running the NFS server daemons.

nfs mount: dbserver:NFS: Service not responding
nfs mount: retrying: /mntpoint

To solve the service not responding errorcondition, complete the following steps:

1.   Enterthe who -rcommand on the server to see if it is at run level 3. If the server is not,change to run level 3 by entering the init 3 command.

2.  Enterthe ps -e commandon the server to check whether the NFS server daemons are running. If they arenot, start them by using the /etc/init.d/nfs.server start script.
 

5. The program not registered Error.The following message appears during the boot process or in response to anexplicit mount request and indicates that an accessible server is not running the mountddaemon.

nfs mount: dbserver: RPC: Program not registered
nfs mount: retrying: /mntpoint

To solve the program not registered errorcondition, complete the following steps:

1.   Enterthe who -rcommand on the server to check that it is at run level 3. If the server is not,change to run level 3 by performing the init 3 command.

2.   Enterthe pgrep -xl mountd command.If the mountd daemonis not running, start it using the /etc/init.d/nfs.server script, first with the stop flag andthen with the start flag.

3.   Checkthe /etc/dfs/dfstabfile entries.
 

6. The stale NFS file handle Error. Thefollowing message appears when a process attempts to access a
remote file resource with an out-of-date file handle.  A possible causefor the stale NFS file handle error is that the file resource on the servermoved. To solve the stale NFS file handle error condition, unmount and mountthe resource again on the client.
 

7. The unknown host Error. 

Thefollowing message indicates that the host name of the server on theclient is missing from the hosts table.

nfs mount: sserver1:: RPC: Unknown host

To solve the unknown host error condition, verifythe host name in the hosts database that supports the client node. Note – Thepreceding example misspelled the node name server1 as sserver1.
 

8. The mount point Error. 

Thefollowing message appears during the boot process or in response to
an explicit mount request and indicates a non-existent mount point.

mount: mount-point /DS9 does not exist.

To solve the mount point error condition, checkthat the mount point exists on the client. Check the spelling of the mountpoint on the command line or in the /etc/vfstab file on the client, or comment out
the entry and reboot the system.
 

9. The no such file Error. 

Thefollowing message appears during the boot process or in response to
an explicit mount request, which indicates that there is an unknown file
resource name on the server.
 

10.No such file or directory

Tosolve the no such file error condition, check that the directory exists
on the server. Check the spelling of the directory on the command line or inthe /etc/vfstab file.