From owner-freebsd-current  Sun Apr  2 23: 0:34 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 435F137B98E
	for <freebsd-current@FreeBSD.ORG>; Sun,  2 Apr 2000 23:00:26 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id HAA21497;
	Mon, 3 Apr 2000 07:59:48 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200004030559.HAA21497@freebsd.dk>
Subject: Re: Deadlock with vinum raid5
In-Reply-To: <20000403074300.R59549@freebie.lemis.com> from Greg Lehey at "Apr 3, 2000 07:43:00 am"
To: grog@lemis.com (Greg Lehey)
Date: Mon, 3 Apr 2000 07:59:48 +0200 (CEST)
Cc: ticso@cicely.de (Bernd Walter), vallo@matti.ee,
	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 Greg Lehey wrote:
> > Unfortunately I don't have a toy i386 system ready and testet on alpha.
> > There may be some differences how data corruptions efects on this platform.
> 
> I found a potentially serious bug in the RAID calculations yesterday:
> it assumed that sizeof (int) == 4.  I suspect that it would just slow
> down the calculations, but in any case I've fixed it.

This wont fix it on the i386 where the problem is, and btw I havn't seen
any commits yet...

Have you tried running a RAID5 on intel HW and have INVARIANTS in 
the kernel as I asked you to ??

Have you looked at the dumps I've put up that you asked for ??

-Søren


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