Bug 10030

Summary: NFS errors
Product: [Retired] Red Hat Linux Reporter: jbutera
Component: kernelAssignee: Arjan van de Ven <arjanv>
Status: CLOSED CURRENTRELEASE QA Contact: Brian Brock <bbrock>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.0   
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-12-16 02:55:42 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 jbutera 2000-03-07 16:07:37 UTC 
I've searched both Errata/Bug fixes and solutions database with no luck.

We're running 6.1 with NFS across two boxes - one server, one client.
Each box is on the same subnet and plugged into the same switch.
ping and traceroute routinely produce 0.2ms access times between them.
Hence, I don't think that communication between the boxes is a problem.

However on the client we continually get messages

nfs: server XXX not responding, still trying
nfs: server XXX OK

as well as

nfs: task ##### can't get a request slot.

When I say continually I  mean every 2-3 seconds or more.  The
screen is full.  At any rate, I'm trying to find if there is
a bug, or if there are outside influences which could cause
these problems.
Comment 1 Cristian Gafton 2000-08-09 02:35:10 UTC 
assigned to johnsonm
Comment 2 Alan Cox 2002-12-16 02:55:42 UTC 
NFS has been completely rewritten since this old bug
Closing