From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: bruce@it.usyd.edu.au (Bruce Janson)
Cc: nfs@lists.sourceforge.net
Subject: Re: can't get request slot, write timeout
Date: 12 Aug 2002 20:31:28 +0200 [thread overview]
Message-ID: <shseld4nd33.fsf@charged.uio.no> (raw)
In-Reply-To: <200208121444.g7CEiLB09220@serf0.cs.usyd.edu.au>
>>>>> " " == Bruce Janson <bruce@it.usyd.edu.au> writes:
> The surprising thing about this error condition (which has been
> reported on this list for a number of years now) is that under
> such conditions the Linux NFS client code fails so
> spectacularly. Rather than performance degrading gracefully as
> one might expect from a congested network (or a flaky NIC or a
> marginal cable or a slow receiver or a client kernel RAM
> shortage or ...) the kernel instead emits one or more
> can't get a request slot
> messages and the affected transactions freeze for extended
> periods (hours!).
If you know of a cure-all solution, feel free to send me patches...
Cheers,
Trond
-------------------------------------------------------
This sf.net email is sponsored by: Dice - The leading online job board
for high-tech professionals. Search and apply for tech jobs today!
http://seeker.dice.com/seeker.epl?rel_code=31
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-08-12 18:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-12 14:26 can't get request slot, write timeout Bruce Janson
2002-08-12 17:45 ` Bogdan Costescu
2002-08-12 18:31 ` Trond Myklebust [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-12 2:25 Kenneth Howlett
2002-08-12 12:15 ` Bogdan Costescu
2002-08-12 18:47 ` Trond Myklebust
2002-08-13 10:52 ` Bogdan Costescu
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=shseld4nd33.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=bruce@it.usyd.edu.au \
--cc=nfs@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.