Date: Tue, 20 Jun 2006 15:37:00 -0500 From: Astrodog <astrodog@gmail.com> To: obrien@freebsd.org, "Robert Watson" <rwatson@freebsd.org>, freebsd-current@freebsd.org Subject: Re: Often experiencing nfs server foo:/bar: not responding Message-ID: <2fd864e0606201337k20fe5225qd8ac55d4fa1a3bda@mail.gmail.com> In-Reply-To: <20060620202654.GB45624@dragon.NUXI.org> References: <20060620034229.GA48515@dragon.NUXI.org> <44977E82.8040801@samsco.org> <20060620113745.N35462@fledge.watson.org> <20060620202654.GB45624@dragon.NUXI.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 6/20/06, David O'Brien <obrien@freebsd.org> wrote: > On Tue, Jun 20, 2006 at 11:38:29AM +0100, Robert Watson wrote: > > It's possible the origin of the issue is actually a network driver problem. > > I experience this with a wide range of NICs for the client (nve, bge, > gem), and both bge(4) and sk(4) for the server. > > -- > -- David (obrien@FreeBSD.org) > Q: Because it reverses the logical flow of conversation. > A: Why is top-posting (putting a reply at the top of the message) frowned upon? > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > I see this same behavior on newish 6-STABLE and 7-CURRENT systems, between a FreeBSD server and FreeBSD and Solaris clients.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2fd864e0606201337k20fe5225qd8ac55d4fa1a3bda>