From owner-freebsd-questions Wed Sep 18 2:49:21 2002 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 4CF2937B401 for ; Wed, 18 Sep 2002 02:49:20 -0700 (PDT) Received: from mail.thundernet.cz (mail.thundernet.cz [62.77.87.114]) by mx1.FreeBSD.org (Postfix) with SMTP id B933F43E6E for ; Wed, 18 Sep 2002 02:49:18 -0700 (PDT) (envelope-from neuhauser@bellavista.cz) Received: (qmail 17017 invoked from network); 18 Sep 2002 09:49:08 -0000 Received: from unknown (HELO freepuppy.bellavista.cz) (62.168.44.50) by mail.thundernet.cz with SMTP; 18 Sep 2002 09:49:08 -0000 Received: by freepuppy.bellavista.cz (Postfix, from userid 1001) id D954F2FDAB2; Wed, 18 Sep 2002 11:49:06 +0200 (CEST) Date: Wed, 18 Sep 2002 11:49:06 +0200 From: Roman Neuhauser To: freebsd-questions Subject: NFS: stuck in an uninterruptible system call Message-ID: <20020918094906.GE379@freepuppy.bellavista.cz> Mail-Followup-To: freebsd-questions Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.1i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm sure this is all old news to you: Machine A has mounted a filesystem NFS exported from machine B. Machine B reboots. Anything on box A that tries to access the now gone fs will hang forever. I've read about deficiencies in NFS many times and places, but it's almost impossible to believe that it would be *that* broken. Is it really, or can I get rid of this problem by adding a switch somewhere? If there's no way out inherent to NFS, I'm thinking about scripting around it. Before I sit on this task (pretty big imo), maybe someone already has a workaround. Care to share? -- begin 666 nonexistent.vbs FreeBSD 4.7-RC 11:23AM up 18:37, 17 users, load averages: 2.00, 2.01, 2.00 end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message