From owner-freebsd-questions Fri Oct 30 13:49:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29244 for freebsd-questions-outgoing; Fri, 30 Oct 1998 13:49:26 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29237 for ; Fri, 30 Oct 1998 13:49:23 -0800 (PST) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM ([132.245.135.84]) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/10/01-E) with ESMTP id QAA29119; Fri, 30 Oct 1998 16:48:45 -0500 (EST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id QAA19616; Fri, 30 Oct 1998 16:48:13 -0500 (EST) Received: from tuva.engeast.baynetworks.com (tuva [192.32.68.38]) by pobox.engeast.BayNetworks.COM (SMI-8.6/BNET-97/04/24-S) with ESMTP id QAA04255; Fri, 30 Oct 1998 16:48:14 -0500 for Received: from tuva.engeast.baynetworks.com (localhost [127.0.0.1]) by tuva.engeast.baynetworks.com (8.8.8/8.8.8) with ESMTP id QAA12467; Fri, 30 Oct 1998 16:48:06 -0500 (EST) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199810302148.QAA12467@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-questions@FreeBSD.ORG cc: witr@rwwa.com, bwithrow@BayNetworks.COM Subject: AMD NFS hangs Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 Oct 1998 16:48:06 -0500 From: Robert Withrow Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using 3.0-RELEASE I am experiencing NFS hangs related to AMD mounts of some filesystems. I suspect that this may be related to this message that I got the first time I booted with AMD enabled: "noconn option exists, and was turned OFF! (May cause NFS hangs on some systems...)" I got this for a lot of the filesystems. At this installation we use a *large* database of AMD maps distributed using NIS. We put the "noconn" option in the /defaults map entry because we have to automount a lot of buggy multihomed Sunos systems that return NFS mount requests from an IP address different than the one in the request. Noconn is supposed to work around this problem. I have a number of FreeBSD systems that all use this map setup. The 2.1.6 systems *never* have this problem. The 2.2.6 systems sometimes experience these hangs, but *never* output the above message. The 3.0 system outputs the above message *and* hangs. I suspect that this message just makes explicit something that was already happening in 2.2.6. Anyway, what can I do to resolve this problem? -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message