Bug 193556

Summary:	rhel3/rhel4 nfs problems
Product:	Red Hat Enterprise Linux 3	Reporter:	Thomas J. Baker <tjb>
Component:	nfs-utils	Assignee:	Jeff Layton <jlayton>
Status:	CLOSED WONTFIX	QA Contact:	Ben Levenson <benl>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.0	CC:	staubach, steved
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-10-19 18:43: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 Thomas J. Baker 2006-05-30 15:08:45 UTC

Description of problem:

An up to date RHEL3 client system has problems with nfs to an up to date RHEL4
server. The nfs mounts are automounted. The client system reports "server not
responding" and the user process, like vim, hangs. The client never reports
"server OK" even though the mount seems to recover. A 'df' doesn't hang. But the
process never recovers and two of the four CPUs (two real, two hyperthreaded) go
into near 100% iowait.


Version-Release number of selected component (if applicable):

nfs-utils-1.0.6-43EL
kernel-smp-2.4.21-40.EL

How reproducible:

Happens almost immediately after boot. It has happened as far back as kernel 37.

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Other clients have no problems mounting the same directory (it's a users home
directory) from the server but most of the other clients are running RHEL4.

Comment 1 Jeff Layton 2007-07-17 14:18:38 UTC

Sounds like you might have some networking issues. Is this still an issue with
RHEL3U9?

Comment 2 RHEL Program Management 2007-10-19 18:43:42 UTC

This bug is filed against RHEL 3, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products. Since
this bug does not meet that criteria, it is now being closed.
 
For more information of the RHEL errata support policy, please visit:
http://www.redhat.com/security/updates/errata/
 
If you feel this bug is indeed mission critical, please contact your
support representative. You may be asked to provide detailed
information on how this bug is affecting you.