From owner-freebsd-hackers@FreeBSD.ORG Sun Oct 23 06:19:13 2005 Return-Path: X-Original-To: hackers@freebsd.org Delivered-To: freebsd-hackers@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B160516A41F for ; Sun, 23 Oct 2005 06:19:13 +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 2391543D45 for ; Sun, 23 Oct 2005 06:19:13 +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 j9N6JDmR025991 for ; Sat, 22 Oct 2005 23:19:13 -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 j9N6JC1d003545 for ; Sat, 22 Oct 2005 23:19:12 -0700 (PDT) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.13.4/8.13.4/Submit) id j9N6JBll003544 for hackers@freebsd.org; Sat, 22 Oct 2005 23:19:11 -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: hackers@freebsd.org Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Exit Consulting Date: Sat, 22 Oct 2005 23:19:11 -0700 Message-Id: <1130048351.3442.8.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/1146/Thu Oct 20 21:36:48 2005 on tinker.exit.com X-Virus-Status: Clean Cc: Subject: "panic: initiate_write_inodeblock_ufs2: already started" on 6.0-RC1 with Intel SRCU42L RAID. X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: frank@exit.com List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 23 Oct 2005 06:19:13 -0000 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. -- Frank Mayhar frank@exit.com http://www.exit.com/ Exit Consulting http://www.gpsclock.com/ http://www.exit.com/blog/frank/