From owner-freebsd-current Wed Feb 19 14:51:54 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 6BF3F37B401 for ; Wed, 19 Feb 2003 14:51:53 -0800 (PST) Received: from msgbas2x.cos.agilent.com (msgbas1tx.cos.agilent.com [192.25.240.37]) by mx1.FreeBSD.org (Postfix) with ESMTP id A0EC243F75 for ; Wed, 19 Feb 2003 14:51:51 -0800 (PST) (envelope-from darrylo@soco.agilent.com) Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 4E4482623; Wed, 19 Feb 2003 15:51:51 -0700 (MST) Received: from mina.soco.agilent.com (mina.soco.agilent.com [141.121.54.157]) by relcos2.cos.agilent.com (Postfix) with ESMTP id B52D8AFE; Wed, 19 Feb 2003 15:51:50 -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 OAA05165; Wed, 19 Feb 2003 14:51:50 -0800 (PST) Message-Id: <200302192251.OAA05165@mina.soco.agilent.com> To: Brad Knowles Cc: current@FreeBSD.ORG Subject: Re: background fsck deadlocks with ufs2 and big disk Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 19 Feb 2003 21:34:24 +0100." Mime-Version: 1.0 (generated by tm-edit 1.7) Content-Type: text/plain; charset=US-ASCII Date: Wed, 19 Feb 2003 14:51:49 -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 Brad Knowles wrote: > You know, vinum & softupdates have had bad interactions with each > other for as long as I can remember. Has this truly been a > consistent thing (as I seem to recall), or has this been an > on-again/off-again situation? Ah, yaaah. Hmm .... This is the first I've heard of that, but I can see how that could be. Could vinum be considered to be a form of (unintentional) write-caching? That might explain how the filesystem got terribly hosed, but it doesn't help with the panic. Foo. [ This is on a system that's been running in the current state for around a month. So far, it's panic'd once (a week or so ago), and so I don't have any feel for long-term stability. We'll see how it goes. ] -- 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