Nine common NFS server faults summarized by technical personnel

There are many NFS server faults. This friend summarized nine common NFS server faults for you and hoped to help you.

1. The rpcbind failure error
Fault symptom:
Nfs mount: server1: RPC: Rpcbind failure
RPC: Timed Out
Nfs mount: retrying:/mntpoint
Cause:
First, there may be an incorrect IP address, host name, or node name combination in the hosts file of the client;
Second, the server temporarily stops service due to overload.

2. The server not responding error
Symptom:
NFS server server2 not responding, still trying
Cause:
First, the network is disconnected. Run the ping command to check the problem.
Second, the server is shut down.

3. The NFS client fails a reboot error
Symptom:
After the client is started, the following prompt information is displayed:
Setting default interface for multicast: add net 224.0.0.0: gateway:
Client_node_name.
Cause:
If you use fg in the mount Option of etc/vfstab, you cannot mount the resources on the server. Change it to bg or comment out the row until the server is available.

4. The service not responding error
Symptom:
Nfs mount: dbserver: NFS: Service not responding
Nfs mount: retrying:/mntpoint
Cause:
First, if the current level is not level 3, use who-r to view it and use init to switch.
Second, the NFS Server daemon does not exist. Run ps-ef | grep nfs check and start with/etc/init. d/nfs. server start.

5. The program not registered error
Symptom:
Nfs mount: dbserver: RPC: Program not registered
Nfs mount: retrying:/mntpoint
Cause:
First, the current level is not level 3.
Second, the mountd daemon is not started. Use the/etc/init. d/nfs. server script to start the NFS daemon.
Third, check whether entries in/etc/dfs/dfstab are normal.

6. The stale file handle error
Symptom:
Stale NFS file handle
Cause:
The shared resources on the server are moved. You can use umount and mount on the client to re-mount them.

7. The unknown host error
Symptom:
Nfs mount: sserver1: RPC: Unknown host
Cause:
The content in the hosts file is incorrect.

8. The mount point error
Symptom:
Mount: mount-point/DS9 does not exist.
Cause:
This mount point does not exist on the client. Check the spelling of related entries in the command line or/etc/vfstab file.

9. The no such file error
Symptom:
No such file or directory.
Cause:
This mount point does not exist on the server. Check the spelling of related entries in the command line or/etc/vfstab file.