Bug 59909

Summary:	NFSv3 not really supported
Product:	[Retired] Red Hat Linux	Reporter:	Chris Ricker <chris.ricker>
Component:	nfs-server	Assignee:	Michael K. Johnson <johnsonm>
Status:	CLOSED DEFERRED	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.2	CC:	bcrl, shishz
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2002-02-14 18:29:20 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Chris Ricker 2002-02-14 18:29:14 UTC

Using two RH 7.2 boxes with the 2.4 kernel, attempts to mount NFS over TCP fail,
but the same attempt over UDP works:

station14# mount -o tcp server1:/export/kickstart /mnt/kickstart
nfs server reported server unavailable: Address already in use
station14# mount server1:/export/kickstart /mnt/kickstart
station14#

Not only is the NFSv3 implementation broken, but the error messages are
extremely bizarre.  What about "Address already in use" indicates "server does
not support TCP"?

Comment 1 Michael K. Johnson 2002-03-27 23:26:56 UTC

NFS/TCP is reported to function in later kernels, and will probably
function in an upcoming release.

You can, if you like, test our skipjack beta to confirm.

Comment 2 Chris Ricker 2002-03-28 04:00:15 UTC

It doesn't work with 2.4.18-0.4 on both server and client.

And it still fails with the completely bogus error message.

Comment 3 Seth Vidal 2002-04-13 05:03:34 UTC

2.4.18-0.13 also doesn't work.
though I would be eternally grateful if y'all would patch in neil's server-side
tcp fixes.