Hi,
I had posted something about this earlier one of the responses I received
was that my nfs server does not support tcp over nfs since the output of
rpcinfo -p looked like the following:
[root@client linux-2.4]# rpcinfo -p server
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
391002 2 tcp 32769 sgi_fam
100011 1 udp 705 rquotad
100011 2 udp 705 rquotad
100011 1 tcp 708 rquotad
100011 2 tcp 708 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 33050 nlockmgr
100021 3 udp 33050 nlockmgr
100021 4 udp 33050 nlockmgr
100005 1 udp 33051 mountd
100005 1 tcp 40931 mountd
100005 2 udp 33051 mountd
100005 2 tcp 40931 mountd
100005 3 udp 33051 mountd
100005 3 tcp 40931 mountd
Just for kicks I installed Fedora Core 2 on one of my nfs client machines. I
mounted all drives with proto=tcp and nfsvers=3 and everything worked great.
I ran some tests and I got very good results. Nfs on Fedora was at least
100% faster than on Redhat. All this done using the same nfs server located
on a Redhat 9 Server. My other Redhat 9 clients all with Kernel 2.4.20-31.9
fail to mount with proto=tcp. From the reading I have done most kernels
above 2.4.19 are supposed to have nfs over tcp support. I tried recompiling
the kernel on one of the Redhat nfs clients using xconfig; but under the
Network File System options tcp support for nfs was grayed out (disabled). I
am not sure whether this means that is already installed. I have noticed
that other people have had similar problems but I don't see a straight
answer on the forum.
Any and all feedback would be greatly appreciated.
Enils
make sure you have enabled CONFIG_EXPERIMENTAL. it's the very first
menu item in "make xconfig".
-----Original Message-----
From: Enils Bashi [mailto:[email protected]]
Sent: Monday, June 07, 2004 4:04 PM
To: [email protected]
Subject: [NFS] tcp over nfs for redhat 9 kernel 2.4.20-31.9
Hi,
I had posted something about this earlier one of the responses I
received was that my nfs server does not support tcp over nfs since the
output of rpcinfo -p looked like the following:
[root@client linux-2.4]# rpcinfo -p server
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100024 1 udp 32768 status
100024 1 tcp 32768 status
391002 2 tcp 32769 sgi_fam
100011 1 udp 705 rquotad
100011 2 udp 705 rquotad
100011 1 tcp 708 rquotad
100011 2 tcp 708 rquotad
100003 2 udp 2049 nfs
100003 3 udp 2049 nfs
100021 1 udp 33050 nlockmgr
100021 3 udp 33050 nlockmgr
100021 4 udp 33050 nlockmgr
100005 1 udp 33051 mountd
100005 1 tcp 40931 mountd
100005 2 udp 33051 mountd
100005 2 tcp 40931 mountd
100005 3 udp 33051 mountd
100005 3 tcp 40931 mountd
Just for kicks I installed Fedora Core 2 on one of my nfs client
machines. I mounted all drives with proto=tcp and nfsvers=3 and
everything worked great. I ran some tests and I got very good results.
Nfs on Fedora was at least 100% faster than on Redhat. All this done
using the same nfs server located on a Redhat 9 Server. My other Redhat
9 clients all with Kernel 2.4.20-31.9 fail to mount with proto=tcp. From
the reading I have done most kernels above 2.4.19 are supposed to have
nfs over tcp support. I tried recompiling the kernel on one of the
Redhat nfs clients using xconfig; but under the Network File System
options tcp support for nfs was grayed out (disabled). I am not sure
whether this means that is already installed. I have noticed that other
people have had similar problems but I don't see a straight answer on
the forum.
Any and all feedback would be greatly appreciated.
Enils