From owner-cvs-all Mon Sep 20 10:34:27 1999 Delivered-To: cvs-all@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id 8D33915682; Mon, 20 Sep 1999 10:34:20 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id LAA00382; Mon, 20 Sep 1999 11:34:54 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199909201734.LAA00382@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matt Dillon Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_bio.c In-reply-to: Your message of "Mon, 20 Sep 1999 09:19:24 PDT." <199909201619.JAA24480@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Sep 1999 11:34:54 -0600 From: "Justin T. Gibbs" Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk >dillon 1999/09/20 09:19:24 PDT > > Modified files: > sys/kern vfs_bio.c > Log: > Fix bug in brelse() regarding redirtying buffers on B_ERROR. brelse() > improperly ignored the B_INVAL flag when acting on the B_ERROR. > If both B_INVAL and B_ERROR are set the buffer is typically out of the > underlying device's block range and must be destroyed. If only B_ERROR > is set (for a write), a write error occured and operation remains as it > was before: the buffer must be redirtied to avoid corrupting the > filesystem state. If a device "goes away", how should any pending buffers be marked? Does a umount -f cause pending buffers to be B_INVAl'ed? I'm pretty sure that we still can't rid the system of the knowledge of a mounted fs for a device that has disappeared, but I haven't checked recently. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message