Date: Tue, 07 Mar 2000 21:56:27 -0800 From: Doug Barton <DougB@simplenet.com> To: Erez Zadok <ezk@cs.columbia.edu> Cc: Kirk McKusick <mckusick@flamingo.McKusick.COM>, fs@FreeBSD.ORG Subject: Re: changing mount options still can cause damage? Message-ID: <38C5EB8B.89F336B0@simplenet.com> References: <200003072315.SAA04578@shekel.mcl.cs.columbia.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
Erez Zadok wrote:
> 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...
I would be heartily in favor of this as well, for "regular" NFS as well
as amd. Having to reboot a machine to fix a hung mount just chaps my
hide.
Doug
--
"Welcome to the desert of the real."
- Laurence Fishburne as Morpheus, "The Matrix"
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?38C5EB8B.89F336B0>