From owner-freebsd-current Fri Sep 4 10:31:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25086 for freebsd-current-outgoing; Fri, 4 Sep 1998 10:31:35 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from post.mail.demon.net (post-11.mail.demon.net [194.217.242.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25066 for ; Fri, 4 Sep 1998 10:31:29 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from [158.152.46.40] (helo=ragnet.demon.co.uk) by post.mail.demon.net with smtp (Exim 2.02 #1) id 0zEzgj-0002Md-00; Fri, 4 Sep 1998 17:30:22 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0zEq1S-0002NH-00; Fri, 4 Sep 1998 08:11:06 +0100 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19980903192610.36464@futuresouth.com> Date: Fri, 04 Sep 1998 08:11:06 +0100 (BST) From: Duncan Barclay To: "Matthew D. Fuller" Subject: Re: NFS stable before release? Cc: current@FreeBSD.ORG, Greg Lehey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 04-Sep-98 Matthew D. Fuller wrote: > (trim, CC's, trim!) > > On Fri, Sep 04, 1998 at 09:39:49AM +0930, Greg Lehey woke me up to tell me: >> >> I haven't been able to use NFS between two specific systems for about >> two months now. It seems to be related to mount: mounts will only >> succeed about one time out of three. If they don't succeed, a second >> attempt will invariably hang the machine. It's unrelated to the >> system running on the client machine (2.2.[567] or -CURRENT), and >> other machines can mount on the server machine with no problems. I've >> tried changing just about everything on the client machine, including >> the Ethernet board, but the problem remains. About the only thing I >> could think of is the cable length between the machines, but that >> hasn't changed. I've done some tcpdump traces which show that the >> server is returning a "port not reachable" error, but I haven't had >> time to follow all the way through the stack. If anybody has some >> ideas on this one, I'd be really pleased to help fix it. > > I had this problem a good bit a while back. > Not quite sure how I solved it... but it was one of these > A) portmapper problem; kill and restart the nfsd's/nfsiod's > B) DNS problem; specify export by IP address > There also the fact the NFS library binds the rpc code to the the _first_ interface that is marked as being up. This can be a problem if it is, for example, a point to point interface port with nothing on the other end. I posted some pr's and to -hackers about 1year ago on this. Duncan --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message