From owner-freebsd-questions@FreeBSD.ORG Thu Oct 13 19:54:55 2005 Return-Path: X-Original-To: questions@freebsd.org Delivered-To: freebsd-questions@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C40116A41F for ; Thu, 13 Oct 2005 19:54:55 +0000 (GMT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (spoon.beta.com [199.165.180.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id EA97543D46 for ; Thu, 13 Oct 2005 19:54:54 +0000 (GMT) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.13.3/8.13.3) with ESMTP id j9DJspmn043022 for ; Thu, 13 Oct 2005 15:54:51 -0400 (EDT) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200510131954.j9DJspmn043022@spoon.beta.com> To: questions@freebsd.org Date: Thu, 13 Oct 2005 15:54:51 -0400 From: "Brian J. McGovern" X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on spoon.beta.com Cc: Subject: NFS hangs (client) when rebooted server tries to [re]mount filesystem X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Oct 2005 19:54:55 -0000 All, I'm seeing an odd problem while using a FreeBSD system as a Solaris jumpstart system. If I run a client box through the process, its fine the first time. However, if there is an error, or I'm testing, subsequent passes hang up right around the time it should be trying to do an NFS mount. Rebooting the server (FreeBSD 5.4) and restarting the jumpstart process on the client cleans the issue up, and it runs through again (once) fine. Upon running "showmount localhost" after a good pass, I see that the server is registered, even after its been booted, powered off for some time, etc. I expect this is because its not properly doing a unmount. However, the registration can persist for days. I don't have the lock or stat daemons running (didn't see a need), but that may be next on my things to do. Has anyone seen this before? Is there a way to flush this list, or see what may be causing the client to lock up? I've seen the notes in the bootparams file about setting up an all-0s alias for SunOS broadcast, and have done that, as well. Suggestions? -Brian