Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 Apr 1999 10:26:40 -0700 (PDT)
From:      Matthew Dillon <dillon@apollo.backplane.com>
To:        Alfred Perlstein <bright@rush.net>
Cc:        Kevin Day <toasty@home.dragondata.com>, current@FreeBSD.ORG
Subject:   Re: Alright, who's the smart alleck that fixed NFS this last week? :) , WAS: Re: solid NFS patch #6 avail for -current - need tester
Message-ID:  <199904211726.KAA06851@apollo.backplane.com>
References:   <Pine.BSF.3.96.990421120317.11384t-100000@cygnus.rush.net>

next in thread | previous in thread | raw e-mail | index | archive | help
:> We all owe Matt big for this. :)
:> 
:> 
:> > I'm using the default mount operations, as far as NFS server
:> > not responding messages, i have no clue, but the server is still
:> > up and i've seen that message happen when a lot of pressure is
:> > being put on an NFS server even though everything is fine.
:> 
:> Try mounting with -d... Can I make a guess that the NFS mount is going over
:> 100MB ethernet? I have a strong theory that the dynamic retransmit timer
:> needs rework for low latency connections, with high variability in their
:> performance during high traffic. (lots of collisions)
:
:Hmmm, well the client/server are both on 100mbit
:full duplex switched ethernet, fxp0<->fxp0 with no load
:other than the build going on.
:
:-Alfred

    I think Kevin is right re: the dynamic retransmit timeout.  I've
    noticed it occuring on my systems too -- although without the lockups.
    But Kevin has other problems w/ his network that could be contributing
    to the problems he is experiencing.

:btw, just finished run 4 of buildworld, still kicking.

    I've gone through 4 buildworlds so far without any errors using an
    NFS mounted /usr/src and /usr/obj.  Though, I must say, it takes
    about twice as long as with a FFS+softupdates /usr/obj ( two hours verses
    50 minutes ).  The read optimization is very good, though.


					Matthew Dillon 
					<dillon@backplane.com>


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904211726.KAA06851>