From owner-freebsd-current Sun Dec 3 4:38:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from peitho.fxp.org (peitho.fxp.org [209.26.95.40]) by hub.freebsd.org (Postfix) with ESMTP id 963BE37B404 for ; Sun, 3 Dec 2000 04:21:03 -0800 (PST) Received: from earth.causticlabs.com (oca-c1s1-07.mfi.net [209.26.94.8]) by peitho.fxp.org (Postfix) with ESMTP id 4223913611 for ; Sun, 3 Dec 2000 07:21:07 -0500 (EST) Received: by earth.causticlabs.com (Postfix, from userid 1000) id 08B881F23; Sun, 3 Dec 2000 07:21:30 -0500 (EST) Date: Sun, 3 Dec 2000 07:21:30 -0500 From: Chris Faulhaber To: freebsd-current@FreeBSD.org Subject: unexpected vn driver lock Message-ID: <20001203072130.A86631@earth.causticlabs.com> Mail-Followup-To: Chris Faulhaber , freebsd-current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ran a 'make release' last night on -current (NODOC and NOPORTS set). This morning, I find the following: unexpected vn driver lock: 0xc6312500: type VREG, usecount 2, writecount 1, refcount 270, flags (VOBJBUF) tag VT_UFS, ino 492145, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc6312500: type VREG, usecount 2, writecount 1, refcount 253, flags (VOBJBUF) tag VT_UFS, ino 492145, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 unexpected vn driver lock: 0xc65ed500: type VREG, usecount 2, writecount 1, refcount 212, flags (VOBJBUF) tag VT_UFS, ino 492149, on dev #ad/0x40004 (116, 262148) lock type inode: EXCL (count 1) by pid 4 The release seemed to have completed successfully, though. -- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message