From owner-freebsd-current@FreeBSD.ORG Sun Jan 25 06:38:45 2004 Return-Path: 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 E3C3416A4CE; Sun, 25 Jan 2004 06:38:45 -0800 (PST) Received: from server019.webpack.hosteurope.de (server019.webpack.hosteurope.de [80.237.130.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id AB05043D1F; Sun, 25 Jan 2004 06:38:43 -0800 (PST) (envelope-from bfischer@Techfak.Uni-Bielefeld.DE) Received: from no-support.loc (p5082BAD4.dip.t-dialin.net [80.130.186.212]) (authenticated bits=0)i0PEcemC008118; Sun, 25 Jan 2004 15:38:41 +0100 Received: from frolic.no-support.loc (localhost.no-support.loc [127.0.0.1]) by no-support.loc (8.12.9/8.12.9) with ESMTP id i0PEd8fh000515; Sun, 25 Jan 2004 15:39:08 +0100 (CET) (envelope-from bjoern@frolic.no-support.loc) Received: (from bjoern@localhost) by frolic.no-support.loc (8.12.9/8.12.9/Submit) id i0PEd7te000514; Sun, 25 Jan 2004 15:39:07 +0100 (CET) (envelope-from bjoern) From: Bjoern Fischer Date: Sun, 25 Jan 2004 15:39:07 +0100 To: Stephan Uphoff Message-ID: <20040125143907.GA460@frolic.no-support.loc> References: <200312211039.FAA21799@stups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312211039.FAA21799@stups.com> User-Agent: Mutt/1.4.1i cc: Robert Watson cc: current@freebsd.org Subject: Re: getblk(): panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Jan 2004 14:38:46 -0000 Hello, > This looks like a ufs2 snapshot bug when initializing more > inodes in a cylinder group. > bawrite for newly initialized inode block is called while the thread > still owns the cylinder group block. > The snapshot copy-on-write code tries to save the old (uninitialized) > block and might need the cg block to do so => panic. > > Not saving the uninitialized inode block does not look like an > option as inode access functions do not check the cg for cg_initediblk. > > The ugly patch below calls the bawrite for the inode block after > it releases (bdwrites) the cg block and should prevent the panic. is this issue resolved already? I just got a panic with latest -CURRENT that looks exactly the same. The machine paniced while performing background fsck on a very busy file system. If I can reproduce the panic I will try your patch. Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------