From owner-freebsd-questions Wed Oct 28 00:46:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06060 for freebsd-questions-outgoing; Wed, 28 Oct 1998 00:46:46 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from dview.roma.reuters. (net144-105.mclink.it [195.110.144.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06052 for ; Wed, 28 Oct 1998 00:46:38 -0800 (PST) (envelope-from masotti@mclink.it) Received: from gatekeeper (gatekeeper [192.168.100.249]) by dview.roma.reuters. (8.8.5/8.6.12) with SMTP id KAA08463; Wed, 28 Oct 1998 10:49:38 +0100 (MET) Message-ID: <3636E827.31DFF4F5@mclink.it> Date: Wed, 28 Oct 1998 09:47:19 +0000 From: Marco Masotti X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 2.2.7-STABLE i386) MIME-Version: 1.0 To: Doug White CC: questions@FreeBSD.ORG Subject: Re: NFS client umount from a not responding server References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White wrote: > Not on a hard mount. :-( You'll have to restore the original server or > reboot the client. > Doug, I don't now whether this is a bug or not, but either NFS clients in a 2.1.7/2.2.5 distribution, when they reboot in such a state of hunging from NFS server not responding, the machine apparently does a shutdown, but no so grafefully: The files systems claims to sync with the usual highlighted message on the console, but then just hangs and the only cure is to power-cycle the box. This is not nice, especially when you need to reboot remotely and then the machine becomes completely unavailable. Thanks -MArco To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message