From owner-freebsd-current Sun Apr 2 8:41:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 473EA37BE0C for ; Sun, 2 Apr 2000 08:41:48 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.9.3/8.9.3) with ESMTP id RAA18517; Sun, 2 Apr 2000 17:40:10 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.9.3/8.9.0) with ESMTP id RAA30096; Sun, 2 Apr 2000 17:41:09 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id RAA25261; Sun, 2 Apr 2000 17:42:16 +0200 (CEST) (envelope-from ticso) Date: Sun, 2 Apr 2000 17:42:16 +0200 From: Bernd Walter To: Bernd Walter Cc: Greg Lehey , Soren Schmidt , vallo@matti.ee, freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 Message-ID: <20000402174216.B25194@cicely8.cicely.de> References: <20000331212544.A59295@myhakas.matti.ee> <200003311932.VAA70873@freebsd.dk> <20000401091140.A51727@freebie.lemis.com> <20000402011538.B24134@cicely8.cicely.de> <20000402015016.C24134@cicely8.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000402015016.C24134@cicely8.cicely.de>; from ticso@cicely.de on Sun, Apr 02, 2000 at 01:50:16AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Apr 02, 2000 at 01:50:16AM +0200, Bernd Walter wrote: > On Sun, Apr 02, 2000 at 01:15:39AM +0200, Bernd Walter wrote: > > > > Greg - I'm using vinums raid5 code since months now for FreeBSDs CVS-Tree on > > 7x 200M disks - it does not hang for me since a long time. > > The latest current I tested R5 well is from 19th March on alpha. That's shortly > > before PHKs changes - I don't beleave that it introduced something new. > > The only problem with R5 I know of is parity corruption because of a bug in > > lockrange() for which I've already send you a fix. Even it is a general bug it > > seems only to cause problems together with softupdates. > > Ops - I oversaw that this happened with a recent current. > The best I can say is that it is likely that it happened after the 19th March. I build a recent current and tested it with R5 and still don't see any hangs. 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. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message