From owner-freebsd-current@FreeBSD.ORG Thu Dec 11 15:52:37 2003 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 188DB16A4CF for ; Thu, 11 Dec 2003 15:52:37 -0800 (PST) Received: from main.gmane.org (main.gmane.org [80.91.224.249]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EA1D43D1F for ; Thu, 11 Dec 2003 15:50:34 -0800 (PST) (envelope-from freebsd-current@m.gmane.org) Received: from root by main.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AUaZe-0001R1-00 for ; Fri, 12 Dec 2003 00:50:26 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-current@freebsd.org Received: from sea.gmane.org ([80.91.224.252]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1AUaQN-0001K3-00 for ; Fri, 12 Dec 2003 00:40:51 +0100 Received: from news by sea.gmane.org with local (Exim 3.35 #1 (Debian)) id 1AUaQN-0005Ok-00 for ; Fri, 12 Dec 2003 00:40:51 +0100 From: Jesse Guardiani Date: Thu, 11 Dec 2003 18:40:51 -0500 Organization: WingNET Lines: 45 Message-ID: References: <200312112212.hBBMC6eF056403@gw.catspoiler.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: usenet@sea.gmane.org User-Agent: KNode/0.7.2 X-Mail-Copies-To: never Sender: news Subject: Re: LOR: ffs_snapshot.c from 5.2-BETA X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jesse@wingnet.net List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 11 Dec 2003 23:52:37 -0000 Don Lewis wrote: > On 11 Dec, Jesse Guardiani wrote: >> Don Lewis wrote: >> >>> On 9 Dec, Jesse Guardiani wrote: >>>> Howdy list, >>>> >>>> Has anyone seen this yet? Happened while I was fsck'ing my >>>> external USB hard drive a few days ago. Didn't see anything >>>> recent like this in the archive (Nov was the closest, but it >>>> looked like a separate issue). >>>> >>>> >>>> acquiring duplicate lock of same type: "vnode interlock" >>>> 1st vnode interlock @ ufs/ffs/ffs_snapshot.c:488 >>>> 2nd vnode interlock @ ufs/ffs/ffs_snapshot.c:491 >>>> Stack backtrace: >>>> backtrace(c06df4ef,c06e3b95,c06eca1f,1eb,246) at backtrace+0x17 >>>> witness_lock(c42b9a28,8,c06eca1f,1eb,c3b48678) at witness_lock+0x672 >>>> _mtx_lock_flags(c42b9a28,0,c06eca16,1eb,c19dbf00) at >>>> _mtx_lock_flags+0xba >>>> ffs_snapshot(c3abbc00,bfbfed88,70,c05482f3,c073f800) at >>>> ffs_snapshot+0x1759 >>> >>> A related LOR was reported a few days ago. I think it is harmless, but >>> I also think I know how to fix it. >> >> Going once... Going twice... > > It's more complicated that I thought at first. I hoping to have some > time to work on it over the holidays. Well at least you understand the problem and are willing to work on it. :) I'm thread ignorant. Hopefully one of my relatives will buy me "Programming with POSIX Threads" by David R. Butenhof, for Christmas so I can stop feeling so useless. :) -- Jesse Guardiani, Systems Administrator WingNET Internet Services, P.O. Box 2605 // Cleveland, TN 37320-2605 423-559-LINK (v) 423-559-5145 (f) http://www.wingnet.net