> > Got that crash again, with sync-on-panic disabled. The interesting thing > is that the stack trace might be corrupted or inaccurate (maybe some tail > recursion optimisation or inlining is going on around): although it seems > to indicate that the panic is the one from "bwrite: need chained iodone" > (which is absurd, as we saw, since bp->bp_xflags == 0), the panic > message is "buffer is not busy???" from bwrite, and indeed we can see > that this is the case (see print of bp->b_lock).
Thomas, excelent! I found the bug with this information. I improperly unlocked the cluster buf instead of the target buf in a case where the target buf could not be clustered. It's fixed now though. Thanks for the debuging help! Cheers, Jeff To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
