From owner-freebsd-hackers Wed Nov 18 14:35:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20534 for freebsd-hackers-outgoing; Wed, 18 Nov 1998 14:35:51 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns1.BayNetworks.COM [134.177.3.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20420 for ; Wed, 18 Nov 1998 14:35:27 -0800 (PST) (envelope-from bwithrow@BayNetworks.COM) Received: from mailhost.BayNetworks.COM (h016b.s86b1.BayNetworks.COM [134.177.1.107] (may be forged)) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/09/30-E) with ESMTP id OAA15132; Wed, 18 Nov 1998 14:29:13 -0800 (PST) Received: from pobox.engeast.BayNetworks.COM (pobox.engeast.baynetworks.com [192.32.61.6]) by mailhost.BayNetworks.COM (8.9.1/8.8.8) with ESMTP id OAA09801; Wed, 18 Nov 1998 14:29:12 -0800 (PST) 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 RAA21703; Wed, 18 Nov 1998 17:29:12 -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 RAA25694; Wed, 18 Nov 1998 17:29:08 -0500 (EST) (envelope-from bwithrow@tuva.engeast.baynetworks.com) Message-Id: <199811182229.RAA25694@tuva.engeast.baynetworks.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hackers@FreeBSD.ORG cc: bwithrow@BayNetworks.COM, witr@rwwa.com Subject: AMD/NFS problems with 3.0 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 18 Nov 1998 17:29:07 -0500 From: Robert Withrow Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a problem with NFS/AMD hangs for some filesystems in this large automounted network. (I reported this to questions earlier and got no responses). At first I though this might be related to these messages that went to the log the first time I started amd: noconn option exists, and was turned OFF! (May cause NFS hangs on some systems...) So I tried modifying /usr/src/usr.sbin/amd/include/config.h to play with the USE_CONNECTED_NFS_SOCKETS and USE_UNCONNECTED_NFS_SOCKETS. This doesn't seem to have any effect on the problem. What I have noticed is that these problems appear to be related to "deferred" mounts: bash-2.02# amq -s requests stale mount mount unmount deferred fhandles ok failed failed 10 0 176 0 0 bash-2.02# amq -s requests stale mount mount unmount deferred fhandles ok failed failed 12 0 176 0 0 In the code these are referred to as "dropped" mount requests. Can someone tell me what causes these and what I can do to fix this? -- Robert Withrow -- (+1 978 916 8256) BWithrow@BayNetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message