From owner-freebsd-current Fri Mar 31 11:32:35 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 28B5337B652 for ; Fri, 31 Mar 2000 11:32:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA70873; Fri, 31 Mar 2000 21:32:23 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200003311932.VAA70873@freebsd.dk> Subject: Re: Deadlock with vinum raid5 In-Reply-To: <20000331212544.A59295@myhakas.matti.ee> from Vallo Kallaste at "Mar 31, 2000 09:25:44 pm" To: vallo@matti.ee Date: Fri, 31 Mar 2000 21:32:22 +0200 (CEST) Cc: 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: > Hi > > I have four (4) ATA disks, all same new 20GB IBM 7200rpm models. Intel > Seattle BX2 mobo, PIIX4 controller. I'm not expecting any performance > increase or such, simply want to get my hands on. Ata driver, as the > -current doesn't have wd anymore. > I have raid5 volume laid over four disks, containing /usr filesystem, > stripe unit size 256k. Machine deadlocks very reliably while doing > ordinary buildworld, keyboard is responsive, network also but no disk > I/O happens. I see syncer and bufdaemon in vrlock state; make, ln, > syslogd and dhclient in flswait state. I usually don't see such states. > Sources from which I built the system are todays, before I set up vinum. Yup, Greg and I know of this problem, it also happens with the wd driver and with CAM, so the problem is probably not the driver. I'm investigating this right now, and it looks like vinum is botching a struct buf in action somehow. -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message