Linux Practice strategy: NFS server troubleshooting

In Red Hat Enterprise Linux 5.0 server, if NFS fails, you can check the problem from the following aspects.

1.1 troubleshooting ideas

1) whether the NFS client and server load is too high, and whether the network between the server and the client is normal.

2) the file/etc/exports is correct.

3) restart the NFS or portmap service if necessary.

Run the following command to restart portmap and NFS:

Service portmap restart feedom.net

Service nfs start

4) check whether the mount command or/etc/fstab syntax on the client is correct.

5) check whether the kernel supports the NFS and RPC services.

Common kernel options include CONFIG_NFS_FS = m, CONFIG_NFS_V3 = y, CONFIG _ NFSD = m, CONFIG_NFSD_V3 = y, and CONFIG_SUNRPC = m.

We can use the common network connection and testing tools ping and tracerroute to test whether the network connection and speed are normal. The normal network connection is the foundation of NFS. The rpcinfo command is used to display the system's RPC Information. Generally, the-p parameter is used to list the RPC service of a host. When you use the rpcinfo-p command to check the server, you can see portmapper, status, mountd nfs, and nlockmgr. When you use this command to check the client, you should be able to see at least the portmapper service.

1.2 NFS error message

The NFS error information is shown in the following table.

1. Red Hat Enterprise Linux5 virtualization helps Baosteel
2. Verify Linux client identity through Active Directory
3. Linux stands for the netbook market with its price advantages