Shulou(Shulou.com)06/01 Report--

This article mainly introduces "how to solve the common faults of the NFS server under the Linux system". In the daily operation, I believe that many people have doubts about how to solve the common problems of the NFS server under the Linux system. The editor consulted all kinds of materials and sorted out the simple and easy-to-use operation methods. I hope it will be helpful to answer the doubts of "how to solve the common faults of the NFS server under the Linux system". Next, please follow the editor to study!

NFS, whose full name is Network File System and network file system in Chinese, is a part of the distributed file system of Linux and UNIX systems, which can share remote file systems on different networks. NFS was developed by Sun Company and has become one of the standards of document service (RFC1904,RFC1813). Its biggest function is that computers with different operating systems can share data through the network, so NFS can be regarded as a file server. The disadvantage of NFS is that its read and write performance is worse than that of the local hard drive.

1. Common troubleshooting of NFS service:

The NFS service failed. Check the reasons from the following aspects:

(1) check whether the load of NFS client and server is too high, and whether the network between Server and Client is normal.

(2) check the correctness of / etc/exports file

(3) restart NFS and portmap services if necessary

(4) restart portmap and NFS by running the following command:

The code is as follows:

# / etc/init.d/portmap restart

# / etc/init.d/nfs restart

# / etc/init.d/rpcbind restart (in RHEL/CentOS 6.x)

# chkconfig portmap on

# chkconfig nfs on

# chkconfig rpcbind on (in RHEL/CentOS 6.x)

Note: in RHEL/CentOS 6.x, the portmap service has been renamed to the rpcbind service; by the way, the rpcbind service is also a key basic service of the graphical interface, and cannot start the graphical desktop without starting this service.

(5) check whether the syntax of the mount command or / etc/fstab on Client is correct

(6) check whether the kernel supports NFS and RPC services. Normally installed Linux systems will support NFS and RPC services by default, unless you recompile the kernel yourself and do not select the nfs support option to compile.

2. Solutions to common failures in NFS:

1 、 The rpcbind failure error

Failure phenomenon:

The code is as follows:

Nfs mount: server1:: RPC: Rpcbind failure

RPC: Timed Out

Nfs mount: retrying: / mntpoint[ / code]

Reason:

First, it may be because there is an incorrect combination of ip address, hostname, or node name in the client's hosts file

Second, the server is temporarily out of service because of overload.

2 、 The server not responding error

Phenomenon:

The code is as follows:

NFS server server2 not responding, still trying

Reason:

First, the network is not working. Check it with the ping command.

Second, the server is shut down.

3 、 The NFS client fails a reboot error

Phenomenon:

After starting the client, it stops and constantly displays the following prompt message:

The code is as follows:

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

Client_node_name.

Reason:

If fg is used in the mount option of etc/vfstab and the resource on the server cannot be successfully mount, change it to bg or comment out the line until the server is available.

4 、 The service not responding error

Phenomenon:

The code is as follows:

Nfs mount: dbserver: NFS: Service not responding

Nfs mount: retrying: / mntpoint

Reason:

First, the current level is not level 3, check it with who-r and switch with init 3.

Second, the NFS Server daemon does not exist, check with ps-ef | grep nfs and start with / etc/init.d/nfs start.

5 、 The program not registered error

Phenomenon:

The code is as follows:

Nfs mount: dbserver: RPC: Program not registered

Nfs mount: retrying: / mntpoint

Reason:

First, the current level is not level 3.

Second, the mountd daemon is not started, so start the NFS daemon with the / etc/init.d/nfs script.

Third, see if the entries in / etc/dfs/dfstab are normal.

6 、 The stale file handle error

Phenomenon:

The code is as follows:

Stale NFS file handle

Reason:

The shared resources on the server have been moved, and you can reattach them on the client using umount and mount.

7 、 The unknown host error

Phenomenon:

The code is as follows:

Nfs mount: sserver1:: RPC: Unknown host

Reason:

The content in the hosts file is incorrect.

8 、 The mount point error

Phenomenon:

The code is as follows:

Mount: mount-point / DS9 does not exist.

Reason:

The mount point does not exist on the client, so be careful to check the spelling of the relevant entries in the command line or / etc/vfstab file.

9 、 The no such file error

Phenomenon:

The code is as follows:

No such file or directory.

Reason:

The mount point does not exist on the server, so be careful to check the spelling of related entries on the command line or / etc/vfstab file.

10 、 No route to host

Error phenomenon:

The code is as follows:

# mount 10.10.11.211:/opt/data/xmldb / c2c-web1/data/xmldb-t nfs-o rw

Mount: mount to NFS server '10.10.11.211' failed: System Error: No route to host.

Reason:

The firewall is turned on. Turn off the firewall.

This reason is ignored by many people. If firewalls (including iptables and hardware firewalls) are turned on, NFS uses port 111by default. We first need to check whether this port is open, and also check the settings of TCP_Wrappers.

11 、 Not owner

Phenomenon:

The code is as follows:

# mount-F nfs-o rw 10.10.2.3:/mnt/c2c/data/resinfo2 / data/data/resinfo2

Nfs mount: mount: / data/data/resinfo2: Not owner

Reason:

This is an error when Solaris 10 mounts an earlier version of nfs Times.

Resolve:

Need to use the-o vers=3 parameter

Example:

The code is as follows:

# mount-F nfs-o vers=3 10.10.2.3:/mnt/c2c/data/resinfo2 / data/data/resinfo2

12. RPC: Program not registered & retrying

Phenomenon:

The code is as follows:

Nfs mount: 10.10.2.3:: RPC: Program not registered

Nfs mount: retrying: / data/data/resinfo2

Reason:

The NFS shared side service is not started.

Solution: need to restart the NFS service on the shareside

Linux:

The code is as follows:

Mount: RPC: Program not registered

# / etc/init.d/nfs restart

Solaris:

The code is as follows:

Mount: RPC: Program not registered

# / etc/rc.d/init.d/nfs restart

13. Can't contact portmapper: RPC: Remote system error-Connection refused

Phenomenon:

The code is as follows:

# exportfs-a

Can't contact portmapper: RPC: Remote system error-Connection refused

Reason:

This error message occurs because the portmap on the server side is not started.

Resolve:

The code is as follows:

# / etc/init.d/portmap start

At this point, the study on "how to solve the common failures of the NFS server under the Linux system" is over. I hope to be able to solve your doubts. The collocation of theory and practice can better help you learn, go and try it! If you want to continue to learn more related knowledge, please continue to follow the website, the editor will continue to work hard to bring you more practical articles!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.