Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Apr 2001 10:11:10 -0400 (EDT)
From:      jfh@cise.ufl.edu
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   kern/26878: Kernel panic in nfs subsystem (vrele: negative ref cnt)
Message-ID:  <200104261411.f3QEBAp33921@cedar.cise.ufl.edu>

next in thread | raw e-mail | index | archive | help

>Number:         26878
>Category:       kern
>Synopsis:       Kernel panic in nfs subststem (vrele: negative ref cnt)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Apr 26 07:20:01 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator:     Jim Hranicky (jfh@cise.ufl.edu)
>Release:        FreeBSD 4.2-STABLE i386
>Organization:
University of Florida CISE Department
>Environment:

	- FreeBSD 4.2-STABLE #3: Tue Jan 23 10:54:27 EST 2001
	- 650MHz Pentium III
	- 440 GX motherboard
	- 1 internal LVD SCSI drive
	- 4 external LVD SCSI drives
	- NFS exported partitions created with vinum (multiple
	  single-plex concat partitions)
	- ffs+softupdates

>Description:

	Kernel panic in the nfs subsystem. Here is the trace:

	  db> trace
	  Debugger(c0338723) at Debugger+0x34
	  panic(c033c69c,55,0,0,d6e1dcfc) at panic+0x70
	  vrele(d732bcc0) at vrele+0x92
	  nfsrv_symlink(c7748800,c7e4d100,d5a568a0,d6e1ddfc,0) at nfsrv_symlink+0x1212
	  nfssvc_nfsd(d6e1de5c,807c360,d5a568a0,d5a568a0,2) at nfssvc_nfsd+0x502
	  nfssvc(d5a568a0,d6e1df80,4,0,0) at nfssvc+0x643
	  syscall2(2f,2f,2f,0,0) at syscall2+0x1f1
	  Xint0x80_syscall() at Xint0x80_syscall+0x25

	Unfortunately, I've just upgraded to 4.3-STABLE on my master
	machine, and though I have a dump, I don't have a debugging kernel 
	to go along with it. I tried checking out -STABLE for 01/23/01,
	but no luck (I've probably modified the kernel config since then,
	no backup *sigh*).

	However, this machine did have a filesystem fill up on it prior
	to the panic, and the process writing to it over NFS obviously
	didn't notice, and kept trying repeatedly.

	The machine had been up for 46 days without a problem (and without
	any modifications) before this.

>How-To-Repeat:

	Fill up a filesystem and write to it continuously over NFS?

>Fix:

	Unknown.

>Release-Note:
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200104261411.f3QEBAp33921>