Date: Sun, 20 Oct 2002 12:44:26 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: David Schultz <dschultz@uclink.Berkeley.EDU> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Maxim Sobolev <sobomax@FreeBSD.ORG>, hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <200210201944.g9KJiQTf034148@apollo.backplane.com> References: <3DB048B5.21097613@FreeBSD.org> <28472.1035014051@critter.freebsd.dk> <20021020043706.GA23972@HAL9000.homeunix.com> <200210200457.g9K4vbAE030661@apollo.backplane.com> <20021020051241.GA24293@HAL9000.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
:Then how about trying to solve a slightly easier problem? When
:the filesystem is forcibly unmounted, would it be possible to seek
:out and destroy all busy buffers associated with it that couldn't
:be written? This isn't quite as nice a solution as getting the
:system to automatically give up, but it's better than
:necessitating a reboot to work around the problem.
That seems reasonable to me, though I'm full-up on work and can't do it
myself. You would need a flag to record the fact that an error occured
that only the umount code looks at (the main ERROR flag must be cleared
when the buffer is re-dirtied and cannot be used for this purpose), then
the umount code could pass a flag to vinvalbuf or equivalent to cause
dirty-but-previously-errored-out buffers to be discarded. It would be
about three hour's worth of work for someone to do this (including
testing and review).
-Matt
Matthew Dillon
<dillon@backplane.com>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210201944.g9KJiQTf034148>