From owner-freebsd-questions@FreeBSD.ORG Sun Jun 13 20:00:53 2004 Return-Path: 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 4565916A4CE for ; Sun, 13 Jun 2004 20:00:53 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA47543D49 for ; Sun, 13 Jun 2004 20:00:52 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.12.10/8.12.10) id i5DK0lqC087544; Sun, 13 Jun 2004 15:00:47 -0500 (CDT) (envelope-from dan) Date: Sun, 13 Jun 2004 15:00:47 -0500 From: Dan Nelson To: Palle Girgensohn Message-ID: <20040613200046.GD94119@dan.emsphone.com> References: <1FDA476097EB5EBC0B3F23A3@palle.girgensohn.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1FDA476097EB5EBC0B3F23A3@palle.girgensohn.se> X-OS: FreeBSD 5.2-CURRENT X-message-flag: Outlook Error User-Agent: Mutt/1.5.6i cc: questions@freebsd.org Subject: Re: "unlocking" stale nfs? adding -t to running nfsd? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 13 Jun 2004 20:00:53 -0000 In the last episode (Jun 13), Palle Girgensohn said: > I have an nfs mount mounted without -i or -s (stoopid me!), just > plain mount server:/fs /lfs. This was over a WAN connection, and of > course the connection server<->client broke somehow, and now the > mount is stale. This naturally means that I cannot do ls -l / , since > it hangs forever. Now the question: is there any way to unstale this, > so the machine can go back to normal again, without a reboot? umount -f /mountpoint, and remount it. The only thing I know of that can cause an entire mountpoint to go stale is if the server gets rebooted with a new kernel and it can't determine which filesystem an incoming request is for. Connectivity issues shouldn't cause this. > I should really do this mount with tcp, of course, but found no way > to get a running nfsd to also start accepting tcp (nfsd runs with "-n > 6 -u", no -t). Is there a way to tell a running nfsd to start > accepting tcp connections? Just bounce nfsd after changing nfs_server_flags in rc.conf. -- Dan Nelson dnelson@allantgroup.com