From owner-freebsd-current@FreeBSD.ORG Wed Oct 26 20:35:52 2005 Return-Path: X-Original-To: current@freebsd.org 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 5FE4B16A41F for ; Wed, 26 Oct 2005 20:35:52 +0000 (GMT) (envelope-from frank@exit.com) Received: from tinker.exit.com (tinker.exit.com [206.223.0.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D096043D49 for ; Wed, 26 Oct 2005 20:35:51 +0000 (GMT) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime [206.223.0.5]) by tinker.exit.com (8.13.4/8.13.4) with ESMTP id j9QKZpnE080564 for ; Wed, 26 Oct 2005 13:35:51 -0700 (PDT) (envelope-from frank@exit.com) Received: from realtime.exit.com (localhost [127.0.0.1]) by realtime.exit.com (8.13.4/8.13.4) with ESMTP id j9QKZorL055662 for ; Wed, 26 Oct 2005 13:35:50 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id j9QKZodN055660 for current@freebsd.org; Wed, 26 Oct 2005 13:35:50 -0700 (PDT) (envelope-from frank@exit.com) X-Authentication-Warning: realtime.exit.com: frank set sender to frank@exit.com using -f From: Frank Mayhar To: current@freebsd.org In-Reply-To: <1130048351.3442.8.camel@realtime.exit.com> References: <1130048351.3442.8.camel@realtime.exit.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Wed, 26 Oct 2005 13:35:50 -0700 Message-Id: <1130358950.47465.11.camel@realtime.exit.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 FreeBSD GNOME Team Port X-Virus-Scanned: ClamAV 0.86.2/1148/Tue Oct 25 12:34:12 2005 on tinker.exit.com X-Virus-Status: Clean Cc: Subject: Re: "panic: initiate_write_inodeblock_ufs2: already started" on 6.0-RC1 with Intel SRCU42L RAID. X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 20:35:52 -0000 On Sat, 2005-10-22 at 23:19 -0700, Frank Mayhar wrote: > I ran into this panic this evening; PR entered as kern/87861. The > filesystem that gets this is on an Intel SRCU42L RAID5 array and that > seems to be the important characteristic. This also happens in > 5.4-stable, so it's not something special about 6.0. I can reproduce > this at will so it will be easy for me to help diagnose it. Following up my own email to add a little bit of information. I built the kernel with INVARIANTS and managed to catch a KASSERT() at the beginning of bundirty(): panic: bundirty: buffer 0xd6d6cc00 still on queue 1 Queue 1 is the QUEUE_CLEAN queue, for (from the commentary) "non-B_DELWRI buffers." Somewhat more interesting is this error message from just before the panic. There are 200+ of these messages, but this one appears to be associated with this buffer, since the offset and length match: g_vfs_done():da6s1e[WRITE(offset=63781224448, length=16384)]error = 16 Error 16 is EBUSY. Unfortunately the stack is messed up (apparently because of a panic cascade) so I can't extract a backtrace for this one. A dump of the buf structure is in the PR here: http://www.freebsd.org/cgi/query-pr.cgi?pr=87861 -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/