From owner-freebsd-current Sun Apr 2 15:12:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A5B4837BB3C for ; Sun, 2 Apr 2000 15:12:19 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e32MZwQ14612; Sun, 2 Apr 2000 15:35:58 -0700 (PDT) Date: Sun, 2 Apr 2000 15:35:58 -0700 From: Alfred Perlstein To: Soren Schmidt Cc: Bernd Walter , Vallo Kallaste , freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402153557.O21029@fw.wintelcom.net> References: <20000402124957.M21029@fw.wintelcom.net> <200004021939.VAA73985@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200004021939.VAA73985@freebsd.dk>; from sos@freebsd.dk on Sun, Apr 02, 2000 at 09:39:36PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Soren Schmidt [000402 13:05] wrote: > 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. Took a chance... So far my make world is proceeding fine with a kernel from ~1 hour ago. However I'm only using vinum for striping, not mirroring or RAID-5. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message