From owner-freebsd-net Wed Jun 17 13:33:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00425 for freebsd-net-outgoing; Wed, 17 Jun 1998 13:33:55 -0700 (PDT) (envelope-from owner-freebsd-net@FreeBSD.ORG) Received: from clutch.accrue.com (mail.accrue.com [207.86.139.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00401 for ; Wed, 17 Jun 1998 13:33:51 -0700 (PDT) (envelope-from andy@accrue.com) Received: from seatbelt.accrue.com (seatbelt.accrue.com [207.86.139.217]) by clutch.accrue.com (8.8.7/8.8.5) with ESMTP id NAA07200 for ; Wed, 17 Jun 1998 13:36:19 -0700 (PDT) Received: from accrue.com (localhost.accrue.com [127.0.0.1]) by seatbelt.accrue.com (8.8.5/8.8.5) with ESMTP id NAA03364 for ; Wed, 17 Jun 1998 13:30:17 -0700 (PDT) Message-ID: <35882759.73BE61C5@accrue.com> Date: Wed, 17 Jun 1998 13:30:17 -0700 From: Andrew Sharp Organization: Accrue Software X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: "FreeBSD-Net (FreeBSD.Org) List" Subject: Re: NFS Client hangs between FreeBSD Client and FreeBSD Server References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had a similar problem between two FreeBSD machines, except that there was no mismatch: both client and server were UDP. And it hung all over the place. It seems that two FreeBSD machines alone on a 100MB network had timing problems in the UDP NFS code. Finally figured out that it wasn't using TCP and switching to that fixed the hangs. The real problem is that reading the documentation cover to cover, it is easy to assume that the default must be TCP, because they say don't use UDP unless there is a gun to your head, blah blah, so there is no need to specifically specify that [using the available args]. I don't think the defaults are explicitly specified in the man pages and HOWTOs and what not. Perhaps in the NFS spec, but.... a Graeme Brown wrote: > > Dear Freddijanto > > Thanks for your reply. It fixed my problem straight away. > > Why on earth don't the default nfs client options set in /etc/rc.conf > as shipped with FreeBSD specify that TCP mode is required for the > client. I spent several frustrating days banging my head against an > NFS brick-wall over this one ! Well I am enlightened now. > > Thanks > > Graeme To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message