From owner-freebsd-current Wed Jul 10 4:55:26 2002 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 6C0BE37B400 for ; Wed, 10 Jul 2002 04:55:23 -0700 (PDT) Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id BB68743E54 for ; Wed, 10 Jul 2002 04:55:22 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.12.5/8.12.5) with ESMTP id g6ABt8wr007051; Wed, 10 Jul 2002 04:55:13 -0700 (PDT) (envelope-from dl-freebsd@catspoiler.org) Message-Id: <200207101155.g6ABt8wr007051@gw.catspoiler.org> Date: Wed, 10 Jul 2002 04:55:08 -0700 (PDT) From: Don Lewis Subject: VFS lock error in getnewvnode() To: jroberson@chesapeake.net Cc: current@FreeBSD.ORG In-Reply-To: <20020707024045.J25604-100000@mail.chesapeake.net> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG A box running this morning's -current compiled with DEBUG_VFS_LOCKS coughed up this error part way through a "cvs update" of the ports tree. VOP_GETVOBJECT: xxxxx is not locked but should be The stack trace is: getnewvnode() + 0x182 ffs_vget() + 0x73 ufs_lookup() + 0x10df vfs_vnoperate() + 0x13 ufs_cache_lookup() + 0x516 ufs_vnoperate() + 0x13 lookup() + 0x43b namei() + 0x1e4 lstat() I don't understand this error at all, because there is a call to vn_lock() immediately before the call to VOP_GETVOBJECT(). Once it hit this error, I turned off the vfs_badlock_panic switch, but the console continued to spew VFS lock errors for a variety of different vnode addresses. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message