From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Douglas Furlong <douglas.furlong@firebox.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: NFS server not responding
Date: 02 Dec 2003 10:37:06 -0500 [thread overview]
Message-ID: <shsn0ab5izh.fsf@guts.uio.no> (raw)
In-Reply-To: <1070375865.20333.74.camel@wibbit.firebox.com>
>>>>> " " == Douglas Furlong <douglas.furlong@firebox.com> writes:
> If this was the case then i would agree that there is no
> problem at all, but I am noticing delays of three or four
> seconds when opening up a new mail in Evolution, or downloading
> new mail off of the IMAP server (which get stored in the users
> home directory on the NFS server). When typing in to a mail I
> will find the text freezes for several seconds, which is fine
> for me (touch type with accuracy) but other people that are
> less secure working on PC (read most people I deal with), they
> find this sort of behaviour unacceptable (which i agree with).
Nobody on this list is directly responsible for the Fedore Core 1
kernel, so whining about what is or isn't acceptable in it won't help.
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 have found that all of these error's coincide with the NFS
> server not responding error messages. Before making the changes
That's no surprise, but a <1-2% retransmission frequency
_DOES_NOT_SUFFICE_ to explain an NFS server not responding messageq. If
those retransmissions are randomly distributed (as they should
normally be) then we're talking unnoticable delays.
If, OTOH, the retransmissions are all occurring at once, then that
might explain it ('cos retransmissions follow an exponential rule
w.r.t. timeouts). Such behaviour would indicate a serious bug, but
you still need to identify where: it could be a NIC driver bug, could
be a problem with the scheduler, it could be a hang somewhere,
somebody may be disabling interrupts for long periods of time...
...or it could be an external problem.
So now, what have you tried in order to diagnose this problem? Have
you looked at changing NICs, switches etc? Have you tried alternative
kernel builds w/o all the Fedora NPTL+scheduling stuff (e.g. stock
2.4.23)?
Cheers,
Trond
-------------------------------------------------------
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-02 15:37 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 [this message]
2003-12-04 17:17 ` Steve Dickson
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=shsn0ab5izh.fsf@guts.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=douglas.furlong@firebox.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