From owner-freebsd-questions Sat Feb 20 21:54:52 1999 Delivered-To: freebsd-questions@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id CE60E115F4 for ; Sat, 20 Feb 1999 21:54:10 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.8.8/8.8.8) id AAA16096; Sun, 21 Feb 1999 00:00:08 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199902210500.AAA16096@cc942873-a.ewndsr1.nj.home.com> Subject: Re: NFS Trouble In-Reply-To: <3.0.5.32.19990220200058.05701100@ccsales.com> from "Randy A. Katz" at "Feb 20, 99 08:00:58 pm" To: randyk@ccsales.com (Randy A. Katz) Date: Sun, 21 Feb 1999 00:00:08 -0500 (EST) Cc: cjclark@home.com, questions@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randy A. Katz wrote, > No, I asked what could cause the connecting machine to lock up all > resources (not even a console login works, just locked) from trying to do a > mount. That is really what I want to know here. NFS problems are notorious for completely locking up machines. This happens to me at work when, for whatever reason, I loose network connectivity to a machine serving mine. NFS mount requests typically have very long timeouts. Try the '-b' option of mount_nfs. -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message