From owner-freebsd-questions Thu Jul 20 7:55:45 2000 Delivered-To: freebsd-questions@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 7FF9537B946 for ; Thu, 20 Jul 2000 07:55:42 -0700 (PDT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA15498; Thu, 20 Jul 2000 09:55:19 -0500 (CDT) (envelope-from dan) Date: Thu, 20 Jul 2000 09:55:19 -0500 From: Dan Nelson To: Rasmus Skaarup Cc: freebsd-questions@FreeBSD.ORG Subject: Re: NFS client problem (fwd) Message-ID: <20000720095519.A14294@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline User-Agent: Mutt/1.3.5i In-Reply-To: ; from "Rasmus Skaarup" on Thu Jul 20 15:13:30 GMT 2000 X-OS: FreeBSD 5.0-CURRENT Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jul 20), Rasmus Skaarup said: > Forgot to mention that I'm running 4.1-RC as of 07/17/2000. > > Furthermore, I tried to run tcpdump while nfs mounting the directory and > got the following output: > > ** > 15:07:31.822231 skaarup.intra.xxx.dk.444806954 > pesto.intra.xxx.dk.nfs: 128 access [|nfs] > 15:07:31.822513 petix.intra.xxx.dk.nfs > skaarup.intra.xxx.dk.444806954: reply ok 120 proc-858862898A > ** > > The request is sent to pesto (the cluster service), but the answer comes > from the host, petix. > > Is this the reason why mount_nfs wont mount the directory? Probably. FreeBSD assumes the reply is a forged packet and ignores it. Two reported workarounds are to use TCP mounts, or to use the "noconn" option when mounting. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message