Bug 76942 - Bad: NFS TCP client takes 10 minutes for recovery
Bad: NFS TCP client takes 10 minutes for recovery
Status: CLOSED DUPLICATE of bug 77465
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: nfs-utils (Show other bugs)
2.1
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Stephen Tweedie
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-29 16:24 EST by dan chan
Modified: 2007-11-30 17:06 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-31 11:00:51 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description dan chan 2002-10-29 16:24:02 EST
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 13:22:21 EST

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

Note You need to log in before you can comment on or make changes to this bug.