Date: Mon, 20 Sep 1999 11:34:54 -0600 From: "Justin T. Gibbs" <gibbs@caspian.plutotech.com> To: Matt Dillon <dillon@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern vfs_bio.c Message-ID: <199909201734.LAA00382@caspian.plutotech.com> In-Reply-To: Your message of "Mon, 20 Sep 1999 09:19:24 PDT." <199909201619.JAA24480@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909201734.LAA00382>