Visit Our UNIX and Linux User Community


Unusual NFS mount problem on only ONE client: Red Hat WS Rel 3


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Unusual NFS mount problem on only ONE client: Red Hat WS Rel 3
# 1  
Old 01-16-2009
Unusual NFS mount problem on only ONE client: Red Hat WS Rel 3

This is an unusual situation where I have an NFS server currently serving out MULTIPLE clients over several variants of Linux and UNIX successfully (world permissions) except for a SINGLE client. Even the other Linux (SuSE) clients in the same room are mounting successfully with defaults without incident. Server and workstation are on the same subnet with NO firewall and (I don't believe) any routers between them. The "traceroute" command shows a single hop directly to the server and nothing in between.

THIS client 'just stopped working' and the only error from the /var/log/messages file indicates that it "could not contact the NFS server: operation timed out."

It all gets fixed if I use 'tcp' as the mount option in /etc/fstab and manually, bypassing UDP altogether. However this client had been working up until this week and AFAIK no changes were made to this client. Again, other Linux clients IN THE SAME ROOM and ON THE SAME SWITCH are doing just fine and not having this problem!

Even the client system itself mounts two other NFS file systems from a different server without this workaround (IRIX server, believe it or not) but cannot mount the SuSE server without using the 'tcp' flag and bypassing udp protocol.

Any clues here? I've googled this particular issue in bug reports but to no avail. Here's the output from the client side of what's being served:

rpcinfo -p hardhead
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
390436 1 tcp 9907
390435 1 tcp 9890
390113 1 tcp 7937
390115 1 tcp 8494
100024 1 udp 32771 status
100021 1 udp 32771 nlockmgr
100021 3 udp 32771 nlockmgr
100021 4 udp 32771 nlockmgr
100024 1 tcp 42410 status
100021 1 tcp 42410 nlockmgr
100021 3 tcp 42410 nlockmgr
100021 4 tcp 42410 nlockmgr
390103 2 tcp 9801
390109 2 tcp 9801
390110 1 tcp 9801
390120 1 tcp 9801
390109 2 udp 9715
391060 1 tcp 850
390107 5 tcp 9289
390107 6 tcp 9289
390402 1 tcp 9011
390105 5 tcp 9164
390105 6 tcp 9164
390433 1 tcp 9598
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100005 1 udp 805 mountd
100005 1 tcp 806 mountd
100005 2 udp 805 mountd
100005 2 tcp 806 mountd
100005 3 udp 805 mountd
100005 3 tcp 806 mountd
391029 1 tcp 46557
391030 1 tcp 54937
390104 105 tcp 9420
390430 1 tcp 8334
390429 101 tcp 9183

As you can see, NFS is available on both udp and tcp versions 2 and 3.
# 2  
Old 01-16-2009
As I understand it, TCP is better anyway, given that TCP is tuned on your network for LAN access (see TCP/IP tuning guides).

Still, that doesn't solve the problem.

You didn't mention what was running on the server. What OS, version, distribution, and kernel version, please? On the client, what does "uname -a" report? Also what version of NFS is being used on each? You can use "rpm -qi nfs-tools" or similar to get that information.
# 3  
Old 01-19-2009
uname -a reveals the following from the server:

Linux hardhead 2.6.16.54-0.2.5-smp #1 SMP Mon Jan 21 13:29:51 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux

and the client:

Linux gvic3 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:18:24 EDT 2004 i686 i686 i386 GNU/Linux

The server is running SuSE and the client is running Red Hat.

I know the server is "serving out" NFS versions 2 and 3 (see rpcinfo from above) but I'm not 100% sure what the client is using. rpcinfo for the client reveals the following:

[root@gvic3 root]# rpcinfo -p
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
100021 1 udp 32769 nlockmgr
100021 3 udp 32769 nlockmgr
100021 4 udp 32769 nlockmgr
100021 1 tcp 32769 nlockmgr
100021 3 tcp 32769 nlockmgr
100021 4 tcp 32769 nlockmgr
100007 2 udp 1004 ypbind
100007 1 udp 1004 ypbind
100007 2 tcp 1007 ypbind
100007 1 tcp 1007 ypbind
391002 2 tcp 32770 sgi_fam
100011 1 udp 739 rquotad
100011 2 udp 739 rquotad
100011 1 tcp 758 rquotad
100011 2 tcp 758 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100003 2 tcp 2049 nfs
100003 3 tcp 2049 nfs
100005 1 udp 755 mountd
100005 1 tcp 770 mountd
100005 2 udp 755 mountd
100005 2 tcp 770 mountd
100005 3 udp 755 mountd
100005 3 tcp 770 mountd

I tried the rpm command but didn't get anything under the 'nfs-tools' query.
# 4  
Old 02-09-2009
It occurred to me that both Suse and RedHat distributions have automatic updates. It's possible they automatically updated some server tools which triggered an incompatibility. Did you check to see that modules and tools for nfs are still the same? That is, they have an older timestamp. Post the output of these commands:
Code:
rpm -qi nfs-tools
find /lib/modules -name "nfs.ko" -ls

# 5  
Old 02-12-2009
Quote:
Originally Posted by otheus
It occurred to me that both Suse and RedHat distributions have automatic updates. It's possible they automatically updated some server tools which triggered an incompatibility. Did you check to see that modules and tools for nfs are still the same? That is, they have an older timestamp. Post the output of these commands:
Code:
rpm -qi nfs-tools
find /lib/modules -name "nfs.ko" -ls

I ran this command set on the client, and received zero output as a result.

The rpm query yielded nothing for nfs-tools, and the find command also came back with nothing there either.

The client is definitely not set up for auto updates, as it is connected only internally on corp. LAN and does not access the Internet.

The server is also tightly controlled, and auto-updates are turned off on that system. Updates on that particular NAS server are tightly controlled, here.

As far as I know, no major updates were done to either. The client *could* have had the opportunity to slip by, but I just verified that this client is definitely NOT on the corporate LAN. It is firewalled inside of our "dev-only" network.

Thank you for following up on this.
# 6  
Old 02-12-2009
I'm stumped.

If you have it working with TCP, it is now suggested that be used anyway. It actually has better performance, when the server and client are properly tuned.
# 7  
Old 02-12-2009
Red Hat AS 3 (I guess you can call it RHEL 3, but that's incorrect) has a bug in it's broadcom, tg3 driver, your interface will probably be bouncing a lot... afaik, there is no fix for it. Move to RHEL 4 or 5 if you can.

If you're not using the tg3 driver, then I don't know what the issue is....

I'd avoid RHAS/RHES v3 if at all possible.

Previous Thread | Next Thread
Test Your Knowledge in Computers #964
Difficulty: Medium
HTML4 became a W3C Recommendation in 1994.
True or False?

10 More Discussions You Might Find Interesting

1. Solaris

Solaris 10 NFS client cannot mount a share from a Windows server

I have a Solaris 10 server, I'm trying to mount a share from a Windows nfs server. If I add this entry (tst-walnut:/test_sap_nfs - /majid nfs - yes rw,soft) to my /etc/vfstab, then I can mount, but when I create a file by root:root, the file owner changes to... (1 Reply)
Discussion started by: Hiroshi
1 Replies

2. Shell Programming and Scripting

Mount NFS Share On NFS Client via bash script.

I need a help of good people with effective bash script to mount nfs shared, By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people. The scenario as follow: An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies

3. Solaris

Solaris 10 as a Red Hat IPA Client

Hi We have IPA v3 setup on a Red Hat RHEL6 server and are trying to interface our Solaris servers to it. There is a slight complication in that we are using krb5 for authentication and IPA as a user and access repository (not sure if that makes a difference). The problem is that we cannot get... (4 Replies)
Discussion started by: gregsih
4 Replies

4. Red Hat

Not able to mount NFS share on client side

When i tried to mount the nfs i see this error message mount -t nfs 192.168.20.194:/remote/proj1 /nfsmount mount: 192.168.20.194:/remote/proj1 failed, reason given by server: Permission denied and the /etc/exports file in the host side looks like this /remote/proj1 ... (12 Replies)
Discussion started by: srinathk
12 Replies

5. Red Hat

x-win client connect red hat

Hi, I use red hat linux ES 5.5 32 bit . There is x win(startx) installed. I wan to use XP at another computer and connect the x-win(startx) through IP network . Which software/freeware I can use ??? Please advice .. Is it free ??? (0 Replies)
Discussion started by: chuikingman
0 Replies

6. AIX

can not mount from aix client to linux nfs server

Hi, I am trying to mount a nfs folder from AIX client to Linux NFS Server, but I got the following error: # mount 128.127.11.121:/aix /to_be_del mount: 1831-010 server 128.127.11.121 not responding: RPC: 1832-018 Port mapper failure - RPC: 1832-008 Timed out mount: retrying... (1 Reply)
Discussion started by: victorcheung
1 Replies

7. Red Hat

Oracle client for Red Hat linux on IBM PPC64

Hi , Am trying to install oracle 10g client on Red Hat Linux in an IBM PPC machine. when i try to install during linking am getting the below error My software details : Oracle Version : 10.2.0 Red Hat Version : 5.5 Server Hardware : PPC 64 Error from the logs : /usr/bin/make -f... (7 Replies)
Discussion started by: mugunthanvh
7 Replies

8. Ubuntu

[UBUNTU] mount.nfs fails in Ubuntu / Works on Red Hat!!!

Gurus, I want log in locally to my Lucid (10.04) workstation and have my code saved over the network on my samba account At work, all developers have samba user ids and when we were running Red Hat, we went thru the following procedure to get setup. * open a shell session to NFS server... (2 Replies)
Discussion started by: alan
2 Replies

9. Red Hat

"ERROR : failed to mount nfs source" Red Hat Kickstart

Hi There, I have been googling for this error and try solution provided but still not avail to resolve Kickstart Issue. Any expert have encounter this problem? Thanks. Regards, Regmaster (4 Replies)
Discussion started by: regmaster
4 Replies

10. Shell Programming and Scripting

NFS client Mount script after boot

Hi, I have 12 AIX P series servers. One has the NFS DB2data and the others are client mounts. NFS is not in /etc/filesystem because if NFS DB2data not up the client takes 7+ minutes to give up on nfsmnt and boot up. I'd like to check that nfs is up, then do the client mount all from a startup... (0 Replies)
Discussion started by: sv2xs
0 Replies

Featured Tech Videos