From owner-freebsd-current  Mon Apr  3 10:23:59 2000
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP id 3D04137BCD4
	for <freebsd-current@FreeBSD.ORG>; Mon,  3 Apr 2000 10:23:55 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id TAA00179;
	Mon, 3 Apr 2000 19:23:34 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200004031723.TAA00179@freebsd.dk>
Subject: Re: Deadlock with vinum raid5
In-Reply-To: <200004031707.KAA59737@apollo.backplane.com> from Matthew Dillon at "Apr 3, 2000 10:07:40 am"
To: dillon@apollo.backplane.com (Matthew Dillon)
Date: Mon, 3 Apr 2000 19:23:34 +0200 (CEST)
Cc: vallo@matti.ee, ticso@cicely.de (Bernd Walter),
	freebsd-current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Matthew Dillon wrote:
> :Same story here, but using softupdates or async mounts I can reproduce
> :the hang or panic in less than 60 secs..
> :
> :Vinum with raid5 is plain broken, include INVARIANTS in the kernel
> :and see why...
> :
> :-Søren
> 
>     Hang on to that thought.  As soon as this struct buf mess gets cleared
>     up if Greg hasn't figured out where the bug is I'll throw my lot in
>     to try to speed-up locating and fixing the problem.

Well, there is no need to wait, RELENG_4 is _the_ perfect platform
for this, and the problem has to be fixed there as well....

-Søren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message