Date: Mon, 17 Mar 2003 13:43:26 -0500 (EST) From: Jeff Roberson <jroberson@chesapeake.net> To: Thomas Quinot <thomas@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: bwrite panics solved. Message-ID: <20030317134149.A62387-100000@mail.chesapeake.net> In-Reply-To: <20030317112120.GA71587@melusine.cuivre.fr.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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 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?20030317134149.A62387-100000>