Displaying 2 results from an estimated 2 matches for "nfs_syscalls".
Did you mean:
vfs_syscalls
2006 Mar 13
2
panic: ffs_valloc: dup alloc
I get the above panic after nfs clients attach to this nfs server and
being read/write ops on it after an unclean shutdown. I've fsck'ed the
fs, and it marks it as clean, but I get this every time. It's an NFS
share of a GEOM stripe (about 2TB).
mode = 0100600, inum = 58456203, fs = /mnt
panic: ffs_valloc: dup alloc
I do have dumps from two crashes so far.
This is
2008 Aug 16
0
Panic in nfs/ffs after upgrade from 6.2 to 6.3-RELEASE
...(ap=0x4) at /usr/src/sys/ufs/ffs/ffs_vnops.c:503
#11 0xc09368a0 in VOP_READ_APV (vop=0x4, a=0xc0a9a254) at vnode_if.c:643
#12 0xc07ad086 in nfsrv_read (nfsd=0xc69b3800, slp=0xc520d900, td=0xc532f900, mrq=0xe78e7c98) at vnode_if.h:343
#13 0xc07bd329 in nfssvc_nfsd (td=0x4) at /usr/src/sys/nfsserver/nfs_syscalls.c:474
#14 0xc07bcb08 in nfssvc (td=0xc532f900, uap=0xe78e7d04) at /usr/src/sys/nfsserver/nfs_syscalls.c:181
#15 0xc0924fcb in syscall (frame=
{tf_fs = 59, tf_es = 59, tf_ds = 59, tf_edi = 1, tf_esi = 0, tf_ebp = -1077941464, tf_isp = -410092188, tf_ebx = 4, tf_edx = 672460376, tf_ecx = 25, tf...