Date: Tue, 29 Oct 2002 14:13:14 -0800 From: David Schultz <dschultz@uclink.Berkeley.EDU> To: Poul-Henning Kamp <phk@critter.freebsd.dk> Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Patch to allow a driver to report unrecoverable write errors to the buf layer Message-ID: <20021029221314.GA21640@HAL9000.homeunix.com> In-Reply-To: <97531.1035923533@critter.freebsd.dk> References: <20021029203053.GA21387@HAL9000.homeunix.com> <97531.1035923533@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
Thus spake Poul-Henning Kamp <phk@critter.freebsd.dk>:
> >Recently? I know that the bug was present at least six months
> >ago, and probably earlier as well.
>
> That's "recently" enough for me :-)
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
^^^^^^^^^^^^^^^^^^
Ah yes, I should have guessed. Do you happen to know at what
point it was non-broken? The problem seems nontrivial to fix,
given that you have to be able to propagate the failure up to the
filesystem and cancel all dependent metadata updates in order to
maintain correctness. That's why it seems easier to me to just
destory the failed buffers on unmount, but maybe I'm missing
something.
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?20021029221314.GA21640>