From owner-freebsd-questions Thu Jul 20 20:37:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id E5FCE37B6EA for ; Thu, 20 Jul 2000 20:37:38 -0700 (PDT) (envelope-from djab@enteract.com) Received: from olivia (dschrock.cpe.dsl.enteract.com [216.80.53.93] (may be forged)) by mail.enteract.com (8.9.3/8.9.3) with SMTP id WAA94766; Thu, 20 Jul 2000 22:37:36 -0500 (CDT) (envelope-from djab@enteract.com) Message-ID: <003901bff2c5$474b9cc0$0271a8c0@anonymousdaemon.org> Reply-To: "Daniel Schrock" From: "Daniel Schrock" To: "Dan Nelson" Cc: "freebsd-questions" References: <8l741s$1kdg$1@FreeBSD.csie.NCTU.edu.tw> Subject: Re: NFS client problem (fwd) Date: Thu, 20 Jul 2000 22:39:30 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had the same problem and I know that TCP mounts didn't work, at least on my systems. I never tried noconn so I'm not sure if that would work. I attempted it on a cvsup'd 4.1-RC, and a clean install of both 4.0-20000712-Stable and 4.0-20000717-Stable. Same result in all 3 occasions and a lot of wasted time. In my opinion, the nfs code is broken but my last check of bugs reveaedl no mention of it. Daniel Schrock ----- Original Message ----- From: "Dan Nelson" Newsgroups: mailing.freebsd.questions Sent: Thursday, July 20, 2000 9:58 AM Subject: Re: NFS client problem (fwd) > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message