From owner-freebsd-current Sun Aug 29 23:16:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 550D11504A for ; Sun, 29 Aug 1999 23:16:56 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA10147; Sun, 29 Aug 1999 23:15:47 -0700 (PDT) (envelope-from dillon) Date: Sun, 29 Aug 1999 23:15:47 -0700 (PDT) From: Matthew Dillon Message-Id: <199908300615.XAA10147@apollo.backplane.com> To: Parag Patel Cc: Bernd Walter , Mike Smith , freebsd-current@FreeBSD.ORG, grog@lemis.com Subject: Re: 4.0-CURRENT SMP crash with vinum raid-5 and softupdates References: <80967.935993388@pinhead.parag.codegen.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Greg's debugging this on the machine here at the moment, which is :crashing the same way in what appears to be the same place. : :If anyone else wants to take a crack it, the magic vinum debug number :needed is 328 and not 324. : :So far Greg's discovered that the field is correctly set a little while :before the crash, and then becomes NULL for no apparent reason. Looks :like a really nasty bug. : :The nice thing is this loaner machine has no real job to do besides :crashing, so it can crash as often as required. :) : : : -- Parag I looked at the vinum code a little. I would look for possible situations where the bp may be re-issued as an I/O before actually completing a prior I/O. This could cause the iodone field to be cleared in the middle of an I/O. I don't see anything specific in the code because I don't really understand it yet. That's the best possibility that I can come up with. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message