Bug 76942

Summary: Bad: NFS TCP client takes 10 minutes for recovery
Product: Red Hat Enterprise Linux 2.1 Reporter: dan chan <dchan>
Component: nfs-utilsAssignee: Stephen Tweedie <sct>
Status: CLOSED DUPLICATE QA Contact: Ben Levenson <benl>
Severity: high Docs Contact:
Priority: medium    
Version: 2.1   
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-10-31 16:00:51 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 dan chan 2002-10-29 21:24:02 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; Q312461)

Description of problem:
Bad: NFS TCP client takes 10 minutes or more to recovery an active socket after 
a NFS server failover.

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


How reproducible:
Always

Steps to Reproduce:
1. mount a file system using mount option nfsvers=3, proto=tcp (For 
example /test)
2. mount /test
3. cd /test
4. dd if=/dev/zero of=testdata
5. Failover a NFS server.
	

Actual Results:  It will take 10 to 12 minutes before the nfs client able to 
access the mount point.

Expected Results:  After the NFS server completely failover, NFS client should 
able to access the mount point.

Additional info:

There is a patch in 2.5 kernel fixing this particular problem for NFS client. 
RedHat need to port the patch to AS2.1.
Comment 1 Stephen Tweedie 2002-11-07 18:22:21 UTC 

*** This bug has been marked as a duplicate of 77465 ***