From owner-freebsd-current Mon Apr 3 10: 7:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C918C37B692 for ; Mon, 3 Apr 2000 10:07:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id KAA59737; Mon, 3 Apr 2000 10:07:40 -0700 (PDT) (envelope-from dillon) Date: Mon, 3 Apr 2000 10:07:40 -0700 (PDT) From: Matthew Dillon Message-Id: <200004031707.KAA59737@apollo.backplane.com> To: Soren Schmidt Cc: vallo@matti.ee, ticso@cicely.de (Bernd Walter), freebsd-current@FreeBSD.ORG Subject: Re: Deadlock with vinum raid5 References: <200004030842.KAA63479@freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> 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 Hang on to that thought. As soon as this struct buf mess gets cleared up if Greg hasn't figured out where the bug is I'll throw my lot in to try to speed-up locating and fixing the problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message