From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Charles Lever <Charles.Lever@netapp.com>, nfs@lists.sourceforge.net
Subject: Re: NFS over TCP: random drop
Date: Tue, 16 Mar 2004 20:42:24 +0100 [thread overview]
Message-ID: <20040316194224.GA3262@suse.de> (raw)
In-Reply-To: <1079456730.3045.47.camel@lade.trondhjem.org>
On Tue, Mar 16, 2004 at 12:05:30PM -0500, Trond Myklebust wrote:
> However if the server disconnects us *while we are reconnecting*, then
> the soft request will fail with an EIO. This seems like sensible
> behaviour to me: a server which is accepting a connection then
> immediately breaking it is fundamentally broken...
But the Linux nfsd seems to be doing exactly this - it accepts the
connection, then randomly drops either the oldest or the newest one
(in terms of activity). The one at the head of the queue happens to be
the one we just accepted.
Olaf
--
Olaf Kirch | Stop wasting entropy - start using predictable
okir@suse.de | tempfile names today!
---------------+
-------------------------------------------------------
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
next prev parent reply other threads:[~2004-03-16 19:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-16 16:21 NFS over TCP: random drop Lever, Charles
2004-03-16 17:05 ` Trond Myklebust
2004-03-16 19:42 ` Olaf Kirch [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-16 17:19 Lever, Charles
2004-03-16 11:11 Olaf Kirch
2004-03-16 15:50 ` Trond Myklebust
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040316194224.GA3262@suse.de \
--to=okir@suse.de \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=trond.myklebust@fys.uio.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox