From owner-freebsd-current  Sun Apr  2 12:40:41 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 0CB1137B5CF
	for <freebsd-current@FreeBSD.ORG>; Sun,  2 Apr 2000 12:40:31 -0700 (PDT)
	(envelope-from sos@freebsd.dk)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id VAA73985;
	Sun, 2 Apr 2000 21:39:36 +0200 (CEST)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200004021939.VAA73985@freebsd.dk>
Subject: Re: Deadlock with vinum raid5
In-Reply-To: <20000402124957.M21029@fw.wintelcom.net> from Alfred Perlstein at "Apr 2, 2000 12:49:57 pm"
To: bright@wintelcom.net (Alfred Perlstein)
Date: Sun, 2 Apr 2000 21:39:36 +0200 (CEST)
Cc: ticso@cicely.de (Bernd Walter), vallo@matti.ee (Vallo Kallaste),
	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 Alfred Perlstein wrote:
> > > Just to clearify the things...
> > > Are these problems with 4.0-RELEASE with 4.0-STABLE or with 5.0-CURRENT?
> > 
> > I have the problem with 4.0-RELEASE, STABLE and 5.0-current but it 
> > might only occur with RAID5...
> 
> I've never seen it with just a striped setup:
> Have any of you guys running vinum had any problems with phk's recent
> patches with bio?  Just wanted to know if I should take the plunge.

I dont think vinum is/was usable under -current at least not the 
RAID5 stuff, its broken, and some of it is because greg is not
up to date with what -current looks like these days.

-Søren


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