From owner-freebsd-current  Mon Apr  3  1:42:32 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 7824837BD33
	for <freebsd-current@FreeBSD.ORG>; Mon,  3 Apr 2000 01:42:25 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id KAA63479;
	Mon, 3 Apr 2000 10:42:19 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200004030842.KAA63479@freebsd.dk>
Subject: Re: Deadlock with vinum raid5
In-Reply-To: <20000403102308.A71481@myhakas.matti.ee> from Vallo Kallaste at "Apr 3, 2000 10:23:08 am"
To: vallo@matti.ee
Date: Mon, 3 Apr 2000 10:42:19 +0200 (CEST)
Cc: 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 Vallo Kallaste wrote:
> 
> Here's the sequence of what I did:
> 
> 1. I had i386 system with two 20GB IBM ATA disks and 5.0-current system
> built from March 31 sources. First I used striping over two disks and
> put /usr filesystem onto it, did overnight testing and all was well.
> 2. Same system, same sources plus two same disks. Now I tried raid5 over
> four disks and failed to extract pax archive, got deadlock, not panic.
> 3. Same system, downgraded to 4.0-RELEASE. Raid5 over four disks and I
> failed to extract pax archive, got panic.
> No softupdates.

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


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