From owner-freebsd-current Thu Sep 3 17:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25658 for freebsd-current-outgoing; Thu, 3 Sep 1998 17:27:42 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25653 for ; Thu, 3 Sep 1998 17:27:38 -0700 (PDT) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id TAA02447; Thu, 3 Sep 1998 19:26:10 -0500 (CDT) Message-ID: <19980903192610.36464@futuresouth.com> Date: Thu, 3 Sep 1998 19:26:10 -0500 From: "Matthew D. Fuller" To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: NFS stable before release? References: <199809030541.AAA02169@home.dragondata.com> <9872.904807024@time.cdrom.com> <19980904093949.N606@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19980904093949.N606@freebie.lemis.com>; from Greg Lehey on Fri, Sep 04, 1998 at 09:39:49AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (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 *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message