From owner-freebsd-current Mon Feb 24 10:18:39 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6B1A337B401 for ; Mon, 24 Feb 2003 10:18:38 -0800 (PST) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id ACE5743FE1 for ; Mon, 24 Feb 2003 10:18:37 -0800 (PST) (envelope-from darrylo@soco.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 50AB316625; Mon, 24 Feb 2003 11:18:37 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos1.cos.agilent.com (Postfix) with ESMTP id EC5C215; Mon, 24 Feb 2003 11:18:36 -0700 (MST) Received: from mina.soco.agilent.com (darrylo@localhost [127.0.0.1]) by mina.soco.agilent.com (8.9.3 (PHNE_25184)/8.9.3 SMKit7.1.1_Agilent) with ESMTP id KAA22896; Mon, 24 Feb 2003 10:18:36 -0800 (PST) Message-Id: <200302241818.KAA22896@mina.soco.agilent.com> To: Terry Lambert Cc: current@FreeBSD.ORG Subject: Re: Vinum R5 [was: Re: background fsck deadlocks with ufs2 and big disk] Reply-To: Darryl Okahata In-Reply-To: Your message of "Fri, 21 Feb 2003 01:56:56 PST." <3E55F7E8.BD5BF990@mindspring.com> Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Mon, 24 Feb 2003 10:18:35 -0800 From: Darryl Okahata Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Terry Lambert wrote: > I think this is an expected problem with a lot of concatenation, > whether through Vinum, GEOM, RAIDFrame, or whatever. > > This comes about for the same reason that you can't "mount -u" > to turn Soft Updates from "off" to "on": Soft Updates does not > tolerate dirty buffers for which a dependency does not exist, and > will crap out when a pending dirty buffer causes a write. Does this affect background fsck, too (on regular, non-vinum filesystems)? From what little I know of bg fsck, I'm guessing not, but I'd like to be sure. Thanks. -- Darryl Okahata darrylo@soco.agilent.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Agilent Technologies, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message