On Sunday, 29 August 1999 at 23:15:47 -0700, Matthew Dillon wrote:
>> 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. :)
>
> 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.
Well, I don't do things like that. The only place I reissue a command
is in the iodone routine (complete_rqe or complete_raid5_write; the
latter in this case).
Greg
--
See complete headers for address, home page and phone numbers
finger [EMAIL PROTECTED] for PGP public key
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
