From owner-freebsd-questions Wed Mar 6 11:28:07 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15812 for questions-outgoing; Wed, 6 Mar 1996 11:28:07 -0800 (PST) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA15705 for ; Wed, 6 Mar 1996 11:27:56 -0800 (PST) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id VAA16800; Wed, 6 Mar 1996 21:23:27 +0200 From: John Hay Message-Id: <199603061923.VAA16800@zibbi.mikom.csir.co.za> Subject: Re: When an NFS server croaks... amd? To: dkelly@tomcat1.tbe.com (David Kelly) Date: Wed, 6 Mar 1996 21:23:26 +0200 (SAT) Cc: questions@freebsd.org In-Reply-To: from "David Kelly" at Mar 6, 96 10:59:12 am X-Mailer: ELM [version 2.4 PL24 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org Precedence: bulk > > 140.165.31.92:/disk9/dkelly /disk9 nfs rw,soft,intr,bg 0 0 > > Am using the above line in /etc/fstab to mount an NFS filesystem. At the > moment the remote system has lost its mind. What is the best way to make my > FreeBSD system forget about this mount? "umount -f /disk9" blocks until > something times out. I could comment it out of /etc/fstab and reboot but > that's not sporting. > Try "umount -f 140.165.31.92:/disk9/dkelly". I had the same problem. John -- John Hay -- John.Hay@csir.co.za