strange nfs mounting issue

vinmansbrew · 03-29-2021, 10:52 AM

rhel 7.9 client
rhel 6.10 nfs

So, On 1 server, I have this odd issue with mounting my nfs. It mounts absolutely fine. Fstab is correct, and I have other rhel7 servers working perfectly fine.

The issue comes after a reboot. It won't remount the nfs automatically.

Now this ONLY happens when using the fqdn of the nfs. If I use the IP, then persists after a reboot.

This is the only server that this happens on, and it is a completely fresh install of rhel7.9.

I set up another rhel 7.9 at the same time, no problems like this. I have other rhel 7.9 and they also persist after reboot just fine, using the fqdn.

So, what might be up with this 1 server?

Also, these are all virtual.

shruggy · 03-29-2021, 11:28 AM

See 7.3. Unable to mount a file system in the Linux NFS-HOWTO.

Quote:

[...] Again, if the entries appear correct, check /etc/hosts (or your DNS server) and make sure that the machine is listed correctly, and make sure you can ping the server from the client. Also check the error logs on the system for helpful messages: Authentication errors from bad /etc/hosts.allow entries will usually appear in /var/log/messages, but may appear somewhere else depending on how your system logs are set up. The man pages for syslog can help you figure out how your logs are set up. Finally, some older operating systems may behave badly when routes between the two machines are asymmetric. Try typing tracepath [server] from the client and see if the word "asymmetric" shows up anywhere in the output. If it does then this may be causing packet loss. However asymmetric routes are not usually a problem on recent linux distributions.

If you get the error Remote system error - No route to host, but you can ping the server correctly, then you are the victim of an overzealous firewall. Check any firewalls that may be set up, either on the server or on any routers in between the client and the server. [...]

vinmansbrew · 03-29-2021, 11:44 AM

Tracepath is fine. The client is on a different subnet, but it's on the same subnet the other new server is on.
However, now it appears fine. I didn't change anything, so there may have been something stuck on dns and it just took some additional time.

MadeInGermany · 03-29-2021, 01:26 PM

Ensure there is
hosts: files dns
in /etc/nsswitch.conf

Does /etc/resolv.conf look okay?

dc.901 · 03-29-2021, 02:19 PM

Quote:

Originally Posted by vinmansbrew

The issue comes after a reboot. It won't remount the nfs automatically.

Now this ONLY happens when using the fqdn of the nfs. If I use the IP, then persists after a reboot.

What is output of:

Code:

nslookup <FQDN of nfs server>
OR
host <FQDN of nfs server>

Does the output show correct IP?