2017-11-27 07:31 AM
We are having strange issue with our NFS mount points. We havd FAS2240-4 running 8.2.4P6 7-Mode in HA. And NFS clients are Suse 11.4 x64. Below is issue description.
Mount points of filer 1 are getting stalled on both Suse clients while mount points of filer 2 are running fine on both Suse Clients. After mount points are stalled , i need to remount the mount points of filer 1 again and while doing so i am getting below RPC timed out error and it is getting mounted through UDP. But after doing some read operations it is getting stalled again. But if i have taken a reboot of filer1 it is getting mounted without RPC timed out error. But after some read operations it is getting stalled again.
mount: no type was given - I'll assume nfs because of the colon
mount.nfs: timeout set for Mon Nov 27 16:09:32 2017
mount.nfs: trying text-based options 'addr=10.158.254.53'
mount.nfs: prog 100003, trying vers=3, prot=6
mount.nfs: trying 10.158.254.53 prog 100003 vers 3 prot TCP port 2049
mount.nfs: portmap query retrying: RPC: Timed out
mount.nfs: prog 100003, trying vers=3, prot=17
mount.nfs: trying 10.158.254.53 prog 100003 vers 3 prot UDP port 2049
mount.nfs: prog 100005, trying vers=3, prot=17
mount.nfs: trying 10.158.254.53 prog 100005 vers 3 prot UDP port 4046
10.158.254.53:/vol/v_fs0005 on /mnt type nfs (rw)
I have already check the firewall and there is no firewall between Suse clients and filer 1 . Also telnet is working on NFS ports 2049 and others ports.
2017-12-04 10:13 PM
You could try takeover of node1 (node2 active, node1 down) for some time and if the error persists, there is a configuration issue with node1. If Node2 works fine while in takeover, that means most probably there is a physical network issue. Could be a NIC port of node1, a faulty cable or switch port etc. Do you see any errors in "ifstat" output ?