Date: Tue, 7 Mar 2000 18:15:03 -0500 (EST) From: Erez Zadok <ezk@cs.columbia.edu> To: Kirk McKusick <mckusick@flamingo.McKusick.COM> Cc: Erez Zadok <ezk@cs.columbia.edu>, Alfred Perlstein <bright@wintelcom.net>, Terry Lambert <tlambert@primenet.com>, fs@freebsd.org, jkh@freebsd.org, Bruce Evans <bde@zeta.org.au> Subject: Re: changing mount options still can cause damage? Message-ID: <200003072315.SAA04578@shekel.mcl.cs.columbia.edu> In-Reply-To: Your message of "Mon, 06 Mar 2000 15:14:52 PST." <200003062314.PAA16884@flamingo.McKusick.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003072315.SAA04578>