Subject: nfs panic
To: None <>
From: Tracy Di Marco White <>
List: current-users
Date: 01/29/2001 06:25:24
# cat /kern/version 
NetBSD 1.5.1_ALPHA (LYRA) #2: Sun Jan 28 11:27:07 CST 2001

Sources updated as of Saturday, Jan 27 2001 evening.

The panic happened while running 'du -a' on the exported filesystem on a
Linux machine.  At first it ran fine, but after a short time, it slowed
down and showed I/O errors on a couple of files, at which point we could
no longer get into lyra, we checked and:

panic: nfsd: locking botch in op 3
Stopped in nfsd at breakpoint +0x4: leave
db> t
breakpoint(c563dd84,c01dfd67,c563dd90,100,c563dde8) at breakpoint+0x4
cpu_debugger(c563dd90,100,c563dde8,c0286f18,c03a7824) at cpu_debugger+0x8
panic(c03a7824,3) at panic+0x73
nfssvc_nfsd(c563de30,804b3a0,c54aa32c) at nfssvc_nfsd+0x69c
sys_nfssvc(c54aa32c,c563df74,c563df6c) at sys_nfssvc+0x161b
syscall() at syscall+0x22a
--- syscall (number 155) ---

I have /var/crash/netbsd.1 & /var/crash/netbsd.1.core, I'm just not
familiar with what to do with them yet.  (I'll accept hints.)

The exported filesystem is a 90GB RAID5 filesystem using FFS+softdep,
but I don't think that should be the source of the problem.

Any help would be appreciated.

Tracy J. Di Marco White
Project Vincent Systems Manager