From owner-freebsd-questions@FreeBSD.ORG Sun Jun 13 20:11:43 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 EA82116A4CE for ; Sun, 13 Jun 2004 20:11:43 +0000 (GMT) Received: from rambutan.pingpong.net (81.milagro.bahnhof.net [195.178.168.81]) by mx1.FreeBSD.org (Postfix) with ESMTP id AAB1E43D49 for ; Sun, 13 Jun 2004 20:11:42 +0000 (GMT) (envelope-from girgen@pingpong.net) Received: from localhost (localhost [127.0.0.1])i5DKBbSD035149; Sun, 13 Jun 2004 22:11:37 +0200 (CEST) (envelope-from girgen@pingpong.net) Date: Sun, 13 Jun 2004 22:11:37 +0200 From: Palle Girgensohn To: Dan Nelson Message-ID: In-Reply-To: <20040613200046.GD94119@dan.emsphone.com> References: <1FDA476097EB5EBC0B3F23A3@palle.girgensohn.se> <20040613200046.GD94119@dan.emsphone.com> X-Mailer: Mulberry/3.1.5 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline 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:11:44 -0000 Thanks for the reply! --On Sunday, June 13, 2004 15:00:47 -0500 Dan Nelson wrote: > 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. hmm nfs over WAN genererally sucks... I actually had to reboot the client. :( >> 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. bounce, you mean like kill -USR1 ? Surely, nfsd does not read rc.conf, so kill -USR1 #pid && nfsd -t ...? Is that safe when the server has active clients? /Palle