From: Trond Myklebust <trond.myklebust@fys.uio.no>
Subject: Re: NFS over TCP: random drop
Date: Tue, 16 Mar 2004 10:50:22 -0500
Sender: nfs-admin@lists.sourceforge.net
Message-ID: <1079452222.3045.7.camel@lade.trondhjem.org>
References: <20040316111149.GS25405@suse.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Cc: nfs@lists.sourceforge.net
To: Olaf Kirch <okir@suse.de>
In-Reply-To: <20040316111149.GS25405@suse.de>
Errors-To: nfs-admin@lists.sourceforge.net

P=E5 ty , 16/03/2004 klokka 06:11, skreiv Olaf Kirch:
> Hi,
>=20
> I am looking into an NFS problem at one of our customers. They are
> running NFS over TCP, and the client is some kind of mainframe OS.
>=20
> What happens is this:
>=20
> client:		initiates connections, 3way handshake completes
> server:		closes connection (FIN)
> client:		(at the same moment) sends data to server
> server:		RST
> client:		argh (reports EIO to application)
>=20
> What seems to happen here is the random connection drop in svcsock.c,
> where we randomly drop a connection if the total number of TCP connection=
s
> exceeds (nrthreads + 3) * 10.  "Randomly" here means either the oldest
> connection, or the newest one (which happens to be the one we just
> accepted).
>=20
> The specific problem we have here is that the client doesn't grok TCP RST=
s
> generated by the server. It's arguably a client bug, but I'm nevertheless
> thinking about a way to work around this

It would be a client bug if this was happening on hard mounts, but I
assume this is "soft"?

Cheers,
  Trond


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs