Subject: kern/16142: panic: lfs_vfree: negative bytecount
To: None <gnats-bugs@gnats.netbsd.org>
From: Frank Kardel <kardel@acm.org>
List: netbsd-bugs
Date: 03/31/2002 16:13:31
>Number:         16142
>Category:       kern
>Synopsis:       panic: lfs_vfree: negative bytecount
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Mar 31 06:14:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Frank Kardel
>Release:        NetBSD 1.5ZC-20020330-140522(MET)
>Organization:
	
>Environment:
System: NetBSD pip 1.5ZC NetBSD 1.5ZC (PIP) #0: Sat Mar 30 17:42:34 MET 2002 kardel@pip:/fs/IC35L060-0-a/src/NetBSD/netbsd/sys/arch/i386/compile/PIP i386
Architecture: i386
Machine: i386
>Description:
	During high activity (like cvs update -j ... -j ... on local netbsd tree)
	on an LFS V2 fs a panic is encountered (lfs_vfree: negative bytecount).
	Stack trace (by hand - see PR15947):
	lfs_vfree
	VOP_VFREE
	ufs_inactive
	lfs_inactive
	VOP_INACTIVE
	vrele
	layer_reclaim
	VOP_RECLAIM
	vclean
	vgonel
	getnewvnode
	ffs_vget
	ufs_lookup
	lookup
	namei
	sys___lstat13
	syscall_plain
>How-To-Repeat:
	cvs update -kk -d -j ... -j ... on local netbsd tree after import from cvs current tree...
>Fix:
	Workaround: avoid LFS v2?
>Release-Note:
>Audit-Trail:
>Unformatted: