From owner-freebsd-hackers Tue Oct 29 14:13:19 2002 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1AE3A37B401 for ; Tue, 29 Oct 2002 14:13:18 -0800 (PST) Received: from HAL9000.homeunix.com (12-232-220-15.client.attbi.com [12.232.220.15]) by mx1.FreeBSD.org (Postfix) with ESMTP id 94FEC43E4A for ; Tue, 29 Oct 2002 14:13:17 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: from HAL9000.homeunix.com (localhost [127.0.0.1]) by HAL9000.homeunix.com (8.12.6/8.12.5) with ESMTP id g9TMDETx021672; Tue, 29 Oct 2002 14:13:14 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Received: (from das@localhost) by HAL9000.homeunix.com (8.12.6/8.12.5/Submit) id g9TMDE50021671; Tue, 29 Oct 2002 14:13:14 -0800 (PST) (envelope-from dschultz@uclink.Berkeley.EDU) Date: Tue, 29 Oct 2002 14:13:14 -0800 From: David Schultz To: Poul-Henning Kamp 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> Mail-Followup-To: Poul-Henning Kamp , freebsd-hackers@FreeBSD.ORG References: <20021029203053.GA21387@HAL9000.homeunix.com> <97531.1035923533@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <97531.1035923533@critter.freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thus spake Poul-Henning Kamp : > >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