From owner-freebsd-fs Tue Mar 7 15:15:21 2000 Delivered-To: freebsd-fs@freebsd.org Received: from cs.columbia.edu (cs.columbia.edu [128.59.16.20]) by hub.freebsd.org (Postfix) with ESMTP id 5675937B598; Tue, 7 Mar 2000 15:15:18 -0800 (PST) (envelope-from ezk@shekel.mcl.cs.columbia.edu) Received: from shekel.mcl.cs.columbia.edu (shekel.mcl.cs.columbia.edu [128.59.18.15]) by cs.columbia.edu (8.9.1/8.9.1) with ESMTP id SAA18884; Tue, 7 Mar 2000 18:15:09 -0500 (EST) Received: (from ezk@localhost) by shekel.mcl.cs.columbia.edu (8.9.1/8.9.1) id SAA04578; Tue, 7 Mar 2000 18:15:03 -0500 (EST) Date: Tue, 7 Mar 2000 18:15:03 -0500 (EST) Message-Id: <200003072315.SAA04578@shekel.mcl.cs.columbia.edu> From: Erez Zadok To: Kirk McKusick Cc: Erez Zadok , Alfred Perlstein , Terry Lambert , fs@freebsd.org, jkh@freebsd.org, Bruce Evans Subject: Re: changing mount options still can cause damage? In-reply-to: Your message of "Mon, 06 Mar 2000 15:14:52 PST." <200003062314.PAA16884@flamingo.McKusick.COM> Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200003062314.PAA16884@flamingo.McKusick.COM>, Kirk McKusick writes: [...] > I had contemplated adding a -F (very forcible) > unmount which unmounts without doing any additional I/O operations. > Obviously such a filesystem would be dirty, but it would be > useful if the disk (or NFS server) had died, and you just wanted > the mount gone. Puting my amd-maintainer hat on, such an option would be *extremely* useful to recover from a hung/dead automounter that left "hard" mount points. Since these are virtual mount points created by amd w/o any underlying persistent storage, there really won't be any corruption on disk. The current alternative to recover from a hung/dead amd is a reboot, where all I want is the offending struct vfs nuked with extreme prejudice... > > Kirk Erez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message