From owner-cvs-all Mon Sep 20 11:27: 4 1999 Delivered-To: cvs-all@freebsd.org Received: from proxy4.ba.best.com (proxy4.ba.best.com [206.184.139.15]) by hub.freebsd.org (Postfix) with ESMTP id C471214E50; Mon, 20 Sep 1999 11:26:59 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com ([209.157.86.2]) by proxy4.ba.best.com (8.9.3/8.9.2/best.out) with ESMTP id LAA02829; Mon, 20 Sep 1999 11:19:19 -0700 (PDT) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA83048; Mon, 20 Sep 1999 11:19:19 -0700 (PDT) (envelope-from dillon) Date: Mon, 20 Sep 1999 11:19:19 -0700 (PDT) From: Matthew Dillon Message-Id: <199909201819.LAA83048@apollo.backplane.com> To: "Justin T. Gibbs" Cc: cvs-committers@FreeBSD.ORG, cvs-all@FreeBSD.ORG Subject: Re: cvs commit: src/sys/kern vfs_bio.c References: <199909201734.LAA00382@caspian.plutotech.com> Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk :> 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 At the moment vinvalbuf will write out any dirty buffers, so this is unrelated to the B_INVAL bit, which isn't set yet at this point. The unmount code still calls vinvalbuf with V_SAVE, which is correct, so a forced unmount should not make things work any differently. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message