From owner-freebsd-questions Wed Jan 10 23:09:28 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA06714 for questions-outgoing; Wed, 10 Jan 1996 23:09:28 -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 XAA06616 for ; Wed, 10 Jan 1996 23:06:42 -0800 (PST) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.6.12/8.6.9) id JAA24206 for freebsd-questions@FreeBSD.ORG; Thu, 11 Jan 1996 09:07:07 +0200 From: John Hay Message-Id: <199601110707.JAA24206@zibbi.mikom.csir.co.za> Subject: umnounting a stale nfs mount To: freebsd-questions@FreeBSD.ORG (FreeBSD-questions) Date: Thu, 11 Jan 1996 09:07:06 +0200 (SAT) 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 Hi, I have two machines running FreeBSD 2.1 that mount a volume from a Novell server. Yesterday the disk on the Novell server was changed and now I get the following error when accessing that mount point: --> zibbi:/FreeBSD # ls -l /mikomtek1/vol1 --> ls: /mikomtek1/vol1: Stale NFS file handle I tried to umnount it but got the following error: --> zibbi:/FreeBSD # umount -f /mikomtek1/vol1 --> umount: m1fs28:/vol1: No such file or directory The volume was mounted read-only. Surely you should be able to forcibly umnount a volume even if its server does not exist anymore? Is there anyway short of rebooting the FreeBSD machine to fix this? Our HP unix machines had no trouble umnounting the same volume. John -- John Hay -- John.Hay@csir.co.za