From owner-freebsd-questions Tue Oct 17 15:29:20 1995 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id PAA11441 for questions-outgoing; Tue, 17 Oct 1995 15:29:20 -0700 Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id PAA11429 for ; Tue, 17 Oct 1995 15:29:14 -0700 Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id PAA28713; Tue, 17 Oct 1995 15:23:53 -0700 From: Terry Lambert Message-Id: <199510172223.PAA28713@phaeton.artisoft.com> Subject: Re: Problems with 'df' not doing anything To: pete@puffin.pelican.com (Pete Carah) Date: Tue, 17 Oct 1995 15:23:52 -0700 (MST) Cc: questions@freebsd.org In-Reply-To: from "Pete Carah" at Oct 17, 95 01:41:00 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1018 Sender: owner-questions@freebsd.org Precedence: bulk > Soft mounts are still annoying for 'df'; our timeout is set pretty long. 8-(. > Something that bothers me in freebsd is that you can't force-unmount a > dead hard mount; we should have some provision for that since it leads > to unnecessary dirty reboots. SGI did that one 'right' (it does wait > an inordinate amount of time, like 3-5 minutes per mount, but at least > it unmounts even with a dead server). I think umount -f is supposed to > do this but it doesn't work, at least in 1.1.5 (which is all I've tried > it in). I agree. I noticed the lack of respect for the FORCE flag early on; It's a difficult issue, with client caching, and it's largely unnecessary for local file systems. For local file systems, the problem is one of invalidating the FD; it's tied up in the open file struct bogosties. I think it'd be OK to fixup NFS, leaving the others for later. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.