Date: Sun, 29 Aug 1999 23:15:47 -0700 (PDT) From: Matthew Dillon <dillon@apollo.backplane.com> To: Parag Patel <parag@cgt.com> Cc: Bernd Walter <ticso@cicely.de>, Mike Smith <mike@smith.net.au>, freebsd-current@FreeBSD.ORG, grog@lemis.com Subject: Re: 4.0-CURRENT SMP crash with vinum raid-5 and softupdates Message-ID: <199908300615.XAA10147@apollo.backplane.com> References: <80967.935993388@pinhead.parag.codegen.com>
next in thread | previous in thread | raw e-mail | index | archive | help
: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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908300615.XAA10147>