From: Steve Dickson <SteveD@redhat.com>
To: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: Thu, 04 Dec 2003 12:17:05 -0500 [thread overview]
Message-ID: <3FCF6C11.5010503@RedHat.com> (raw)
In-Reply-To: <shsn0ab5izh.fsf@guts.uio.no>
Trond Myklebust wrote:
>Nobody on this list is directly responsible for the Fedore Core 1
>kernel, ......
>
>
This not completely accurate.... I am responsible for FC1...
And it is my goal to keep FC1 (and beyond) as stable as possible...
>I have no problems on *any* of the machines in the test-rigs I have at
>my disposition when using a standard 2.4.23 kernel. For the record,
>those few that I have used with the Fedora kernel have been fine too
>(though I haven't made any detailed tests of that)
>
>
I not seen this either... FC1 does have the latest retrans improvements
# 03/10/11 trond.myklebust@fys.uio.no 1.1148.17.3
# UDP round trip timer fix. ...
# 03/10/11 trond.myklebust@fys.uio.no 1.1148.17.2
# A request cannot be used as part of the RTO estimation ...
# 03/07/08 trond.myklebust@fys.uio.no 1.1003.1.58
# Back out some congestion control changes that were causing trouble...
With the only difference being FC1 has a longer RTO_MIN
-#define RPC_RTO_MIN (HZ/30)
+#define RPC_RTO_MIN (HZ/10)
And these patches did show a noticeable improvement in bring down the
number of retrans at least in my testing (w/out being overly verbose)
>So now, what have you tried in order to diagnose this problem?
>
>
ifconfig will show if the driver is dropping frames. netstat -s will show
if there are udp fragmentation issues and ethereal is good at showing
whether the ip stack or network are dropping the packets....
SteveD.
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-12-04 17:16 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-27 12:00 NFS server not responding Douglas Furlong
2003-11-27 16:30 ` Trond Myklebust
2003-11-27 19:07 ` Douglas Furlong
2003-11-27 20:02 ` Trond Myklebust
2003-11-28 8:46 ` Juergen Sauer
2003-11-28 9:37 ` Douglas Furlong
2003-11-28 10:11 ` Juergen Sauer
2003-11-28 10:48 ` Douglas Furlong
2003-11-28 12:28 ` Bogdan Costescu
2003-11-28 16:56 ` Trond Myklebust
2003-11-28 18:43 ` Bogdan Costescu
2003-12-02 14:37 ` Douglas Furlong
2003-12-02 15:37 ` Trond Myklebust
2003-12-04 17:17 ` Steve Dickson [this message]
2003-12-04 17:37 ` Steve Dickson
2003-12-04 18:39 ` Trond Myklebust
2003-12-04 19:11 ` Steve Dickson
2003-12-04 20:55 ` seth vidal
2003-12-04 21:24 ` Steve Dickson
2003-12-05 2:53 ` Kyle Rose
2003-12-09 19:47 ` Steve Dickson
2003-12-09 20:09 ` Kyle Rose
2003-12-05 15:50 ` Bogdan Costescu
2003-11-30 20:01 ` seth vidal
2003-12-01 10:58 ` Bogdan Costescu
2003-11-28 12:36 ` Bogdan Costescu
-- strict thread matches above, loose matches on Subject: below --
2009-05-16 0:57 nfs: " Jerome Walters
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=3FCF6C11.5010503@RedHat.com \
--to=steved@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox