From owner-freebsd-current Mon Mar 17 10:43:30 2003 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7986237B404; Mon, 17 Mar 2003 10:43:29 -0800 (PST) Received: from mail.chesapeake.net (chesapeake.net [205.130.220.14]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4059143FBD; Mon, 17 Mar 2003 10:43:28 -0800 (PST) (envelope-from jroberson@chesapeake.net) Received: from localhost (jroberson@localhost) by mail.chesapeake.net (8.11.6/8.11.6) with ESMTP id h2HIhQW63762; Mon, 17 Mar 2003 13:43:27 -0500 (EST) (envelope-from jroberson@chesapeake.net) Date: Mon, 17 Mar 2003 13:43:26 -0500 (EST) From: Jeff Roberson To: Thomas Quinot Cc: current@FreeBSD.ORG Subject: bwrite panics solved. In-Reply-To: <20030317112120.GA71587@melusine.cuivre.fr.eu.org> Message-ID: <20030317134149.A62387-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > 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