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

Today, I will talk to you about how to carry out the abnormal mini-test of linux NFS unmatched host. Many people may not know much about it. In order to make you understand better, the editor has summarized the following contents for you. I hope you can get something according to this article.

Gossip aside, let's get to the test environment, where there are redhat6.7_x64 on both sides.

Click (here) to collapse or open

[root@mytest] # uname-a

Linux mytest 2.6.32-573.el6.x86_64 # 1 SMP Wed Jul 1 18:23:37 EDT 2015 x86 "64 GNU/Linux

Let's take a look at the nfs server configuration. Let's look at the service first.

Click (here) to collapse or open

[root@mytest Packages] # service rpcbind status

Rpcbind (pid 4744) is running...

[root@mytest Packages] # service nfs status

Rpc.svcgssd is stopped-pay attention to this service. Please refer to other articles of this blog for the specific role of stopping status.

Rpc.mountd (pid 5733) is running...

Nfsd (pid 5749 5748 5747 5746 5745 5744 5743 5742) is running...

Rpc.rquotad (pid 5728) is running...

[root@mytest Packages] #

Configuration file:

Click (here) to collapse or open

[root@mytest Packages] # cat / etc/exports

/ soft/db 192.168.8.* (rw,sync,no_root_squash,insecure)

At this point, the client executes MOUNT

Click (here) to collapse or open

[root@mystandby /] # mount-t nfs-o rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,actimeo=0,vers=3,timeo=600 192.168.8.24:/soft/db / soft/database

Mount.nfs: access denied by server while mounting 192.168.8.24:/soft/db

Information output from Syslog

Click (here) to collapse or open

# nfs server Syslog tail-10f / var/log/messages

Jun 26 11:47:41 mytest rpc.mountd [5733]: refused mount request from 192.168.8.25 for / soft/db (/ soft/db): unmatched host

Through some materials, we decided to remove the client IP information from the / etc/hosts file as follows:

Click (here) to collapse or open

# 192.168.8.25 mystandby

There is no need to restart the nfs service. The mount is successful again. On the nfs server side, the resolution of the IP information "*" in the configuration file seems to conflict with the configuration in the hosts file.

What if RAC, or it must be written in the hosts file, OK, let's modify the / etc/exports file and modify it as follows

Click (here) to collapse or open

[root@mytest Packages] # cat / etc/exports

/ soft/db 192.168.8.0 Compact 24 (rw,sync,no_root_squash,insecure)

That is, change "*" to "0pe24" to restart the NFS service, and the MOUNT is normal.

# # Test conclusion: in redhat6.7 (Test Environment), if the IP segment is set to "*" in the nfs exports configuration file, the client IP information cannot be included in the hosts file or "*" can be replaced by "0ram 24".

After reading the above, do you have any further understanding of how to conduct the linux NFS unmatched host abnormal mini-test? If you want to know more knowledge or related content, please follow the industry information channel, thank you for your support.

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.