NetBSD Problem Report #34102

From root@girsa.ro  Fri Jul 28 11:13:02 2006
Return-Path: <root@girsa.ro>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 46EE963B850
	for <gnats-bugs@gnats.NetBSD.org>; Fri, 28 Jul 2006 11:13:02 +0000 (UTC)
Message-Id: <20060728111242.36ABC22AB7@smtp.girsa.ro>
Date: Fri, 28 Jul 2006 14:12:42 +0300 (EEST)
From: kefren@netbsd.ro
Reply-To: kefren@netbsd.ro
To: gnats-bugs@NetBSD.org
Subject: ffs panic in 3.0_STABLE
X-Send-Pr-Version: 3.95

>Number:         34102
>Category:       kern
>Synopsis:       ffs panic in NetBSD 3.0_STABLE
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Jul 28 11:15:00 +0000 2006
>Closed-Date:    Sat Nov 05 16:44:03 +0000 2011
>Last-Modified:  Sat Nov 05 16:44:03 +0000 2011
>Originator:     Mihai Chelaru
>Release:        NetBSD 3.0_STABLE
>Organization:
		None
>Environment:


System: NetBSD ns.girsa.ro 3.0_STABLE NetBSD 3.0_STABLE (Kefren.XENU) #3: Thu Apr 13 21:25:15 EEST 2006 root@ns.girsa.ro:/usr/src/sys/arch/i386/compile/Kefren.XENU i386
Architecture: i386
Machine: i386
>Description:


rsync caused this:

ffs_fsync: dirty: tag VT_UFS(1) type VREG(1), usecount 0, writecount 0, refcount 1, flags (180<VLOCKSWORK,XLOCK,ONWORKLIST>)
        tag VT_UFS, ino 44522527, on dev 142, 3 flags 0x0, effnlink 1, nlink 1
        mode 0100600, owner 32767, group 0, size 100726139 lock type vnlock: EXCL (count 1) by pid 15598.1
panic: vinvalbuf: dirty bufs, vp 0xc8880ddc
Stopped in pid 15598.1 (rsync) at       netbsd:cpu_Debugger+0x4:        leave
cpu_Debugger(c8880ddc,0,c7ae9b4c,0,0) at netbsd:cpu_Debugger+0x4
panic(c038f5f3,c8880ddc,0,c8a0b804,c7ae9b44) at netbsd:panic+0x121
vinvalbuf(c8880ddc,1,ffffffff,c8a0b804,0) at netbsd:vinvalbuf+0xe7
vclean(c8880ddc,8,c8a0b804,4080,c8880ddc) at netbsd:vclean+0x1d8
vgonel(c8880ddc,c8a0b804,2,41,c08381c4) at netbsd:vgonel+0x42
getcleanvnode(c8a0b804,200000,0,c7ae9c78,3c84) at netbsd:getcleanvnode+0xc3
getnewvnode(1,c0750000,c06d0700,c7ae9c78,c8a0b804) at netbsd:getnewvnode+0xc8
ffs_vget(c0750000,337cafd,c7ae9ec4,337cafd,2) at netbsd:ffs_vget+0x50
ffs_valloc(c7ae9cf4,1d55a0d8,3a264486,0,c0379040) at netbsd:ffs_valloc+0xe5
VOP_VALLOC(c8c76888,8180,c7b40690,c7ae9ec4,c8c76888) at netbsd:VOP_VALLOC+0x34
ufs_makeinode(8180,c8c76888,c7ae9ec4,c7ae9ed8,fffffffe) at netbsd:ufs_makeinode+
0x49
ufs_create(c7ae9d84,44b43a9a,c7ae9dbc,c02cabd4,c0378700) at netbsd:ufs_create+0x
26
VOP_CREATE(c8c76888,c7ae9ec4,c7ae9ed8,c7ae9df4,c8c76888) at netbsd:VOP_CREATE+0x
34
vn_open(c7ae9eb4,a03,180,c7b4bce4,0) at netbsd:vn_open+0x132
sys_open(c7b4bce4,c7ae9f64,c7ae9f5c,0,c032fb85) at netbsd:sys_open+0xc7
syscall_plain() at netbsd:syscall_plain+0x18f
--- syscall (number 5) ---
0xbdb47007:
ds          0x11
es          0x11
fs          0x31
gs          0x11
edi         0x1
esi         0x100
ebp         0xc7ae9afc
ebx         0x1
edx         0xc048f000  emul_freebsd_object+0x788cc
ecx         0xffffffe0
eax         0xad9
eip         0xc0320224  cpu_Debugger+0x4
cs          0x9
eflags      0x202
esp         0xc7ae9afc
ss          0x11
netbsd:cpu_Debugger+0x4:        leave
Stopped in pid 15598.1 (rsync) at       netbsd:cpu_Debugger+0x4:        leave
db>


>How-To-Repeat:

	No idea. It happened after about 2 weeks uptime on a heavy load fs.
>Fix:


>Release-Note:

>Audit-Trail:
From: "Juergen Hannken-Illjes" <hannken@netbsd.org>
To: gnats-bugs@gnats.NetBSD.org
Cc: 
Subject: PR/34102 CVS commit: src/sys/kern
Date: Sun, 2 Oct 2011 13:00:08 +0000

 Module Name:	src
 Committed By:	hannken
 Date:		Sun Oct  2 13:00:07 UTC 2011

 Modified Files:
 	src/sys/kern: vfs_vnode.c

 Log Message:
 The path getnewvnode()->getcleanvnode()->vclean()->VOP_LOCK() will panic
 if the vnode we want to clean is a layered vnode and the caller already
 locked its lower vnode.

 Change getnewvnode() to always allocate a fresh vnode and add a helper
 thread (vdrain) to keep the number of allocated vnodes within desiredvnodes.

 Rename getcleanvnode() to cleanvnode() and let it take a vnode from the
 lists, clean and free it.

 Reviewed by: David Holland <dholland@netbsd.org>

 Should fix:
 PR #19110 (nullfs mounts over NFS cause lock manager problems)
 PR #34102 (ffs panic in NetBSD 3.0_STABLE)
 PR #45115 (lock error panic when build.sh*3 and daily script is running)
 PR #45355 (Reader/writer lock error:  rw_vector_enter: locking against myself)


 To generate a diff of this commit:
 cvs rdiff -u -r1.11 -r1.12 src/sys/kern/vfs_vnode.c

 Please note that diffs are not public domain; they are subject to the
 copyright notices on the relevant files.

State-Changed-From-To: open->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 05 Nov 2011 16:44:03 +0000
State-Changed-Why:
Fixed (or if actually not, adequately tracked in the other PRs cited)


>Unformatted:

Home	PR Database Search