Received: from oss.sgi.com (localhost [127.0.0.1])
	by oss.sgi.com (8.12.3/8.12.3) with ESMTP id g5L03wnC013793
	for <linux-xfs-outgoing@oss.sgi.com>; Thu, 20 Jun 2002 17:03:58 -0700
Received: (from majordomo@localhost)
	by oss.sgi.com (8.12.3/8.12.3/Submit) id g5L03w89013791
	for linux-xfs-outgoing; Thu, 20 Jun 2002 17:03:58 -0700
X-Authentication-Warning: oss.sgi.com: majordomo set sender to owner-linux-xfs@oss.sgi.com using -f
Received: from mathserv.math.ohio-state.edu (mathserv.math.ohio-state.edu [128.146.111.31])
	by oss.sgi.com (8.12.3/8.12.3) with SMTP id g5L03hnC013761
	for <linux-xfs@oss.sgi.com>; Thu, 20 Jun 2002 17:03:43 -0700
Received: from mathserv.math.ohio-state.edu (localhost [127.0.0.1])
	by mathserv.math.ohio-state.edu (8.12.3/8.12.3) with ESMTP id g5L06lZL008710
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NOT)
	for <linux-xfs@oss.sgi.com>; Thu, 20 Jun 2002 20:06:47 -0400
Received: (from alden@localhost)
	by mathserv.math.ohio-state.edu (8.12.3/8.12.3/Submit) id g5L06lx8008708
	for linux-xfs@oss.sgi.com; Thu, 20 Jun 2002 20:06:47 -0400
Date: Thu, 20 Jun 2002 20:06:47 -0400
From: Dave Alden <alden@math.ohio-state.edu>
To: linux-xfs@oss.sgi.com
Subject: Kernel oops with XFS and NFS
Message-ID: <20020620200647.A8102@math.ohio-state.edu>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="X1bOJ3K7DJ5YkBrT"
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
X-RAVMilter-Version: 8.3.2(snapshot 20020213) (mathserv)
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
X-Spam-Level: 
Sender: owner-linux-xfs@oss.sgi.com
Precedence: bulk

--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi,
  Help.  I'm having nfsd oops on my system.  I'm currently running
2.4.18-xfs-1.1, but I've tried the CVS as of about 8:30am this morning
(06/20/2002) with similar results.  I'm new to this, but from what I
gather I'm supposed to run ksymoops on the output (retrieved from
dmesg).  I've attached the output of a "ksymoops dmesg.out".  Please
help me, this system is crashing at least once a day.  This system was
totally stable for the past 4 months with 50 users (~100G), so I added
the remainder of my userbase on Tuesday (an additional 450 users, for
a total of 120G).
...thnx,
...dave alden

ps  I tried recompiling with the NFS server as a module, but I keep getting:

    Starting NFS daemon: nfssvc: Function not implemented  

    when I tried to start nfs (with "/etc/init.d/nfs start").  I was hoping
    maybe I'd be able to just unload and reload the module whenever it oops'ed
    instead of rebooting.  :-(

--X1bOJ3K7DJ5YkBrT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="ksymoops.out"

ksymoops 2.4.1 on i686 2.4.18-xfs-1.1.  Options used
     -V (default)
     -k /proc/ksyms (default)
     -l /proc/modules (default)
     -o /lib/modules/2.4.18-xfs-1.1/ (default)
     -m /boot/System.map-2.4.18-xfs-1.1 (default)

Warning: You did not tell me where to find symbol information.  I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc.  ksymoops -h explains the options.

Oops: 0000
CPU:    0
EIP:    0010:[<c01e1687>]    Tainted: P 
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000   ebx: ffffffe8   ecx: c7b9f978   edx: 00000000
esi: c0340300   edi: 00000000   ebp: c7b9f964   esp: f6d65dac
ds: 0018   es: 0018   ss: 0018
Process nfsd (pid: 947, stackpage=f6d65000)
Stack: 00000000 00000000 c71ee55c 00000000 00000008 c71ee55c c01f6c51 f783b800 
       00000000 2a00fa48 00000000 00000000 f6d65e38 00000000 00000000 00000000 
       00000008 00000002 f6d65e5c 00000080 c71ee574 c71ee55c 00000008 c71ee55c 
Call Trace: [<c01f6c51>] [<c01fb1d6>] [<c0207f05>] [<c0149307>] [<c0189f93>] 
   [<c018a3c9>] [<c018a6f9>] [<c018b999>] [<c0190ecc>] [<c0188576>] [<c02da559>] 
   [<c018838f>] [<c0105866>] [<c01881a0>] 
Code: 66 83 bb 4a 01 00 00 00 75 0f 66 83 a3 3c 01 00 00 f7 53 e8 

>>EIP; c01e1687 <xfs_iget+107/150>   <=====
Trace; c01f6c51 <xfs_dir_lookup_int+121/2b0>
Trace; c01fb1d6 <xfs_lookup+96/110>
Trace; c0207f05 <linvfs_lookup+75/c0>
Trace; c0149307 <d_alloc+17/190>
Trace; c0189f93 <nfsd_findparent+33/f0>
Trace; c018a3c9 <find_fh_dentry+1f9/320>
Trace; c018a6f9 <fh_verify+209/400>
Trace; c018b999 <nfsd_access+19/d0>
Trace; c0190ecc <nfsd3_proc_access+ac/c0>
Trace; c0188576 <nfsd_dispatch+b6/17b>
Trace; c02da559 <svc_process+329/4d8>
Trace; c018838f <nfsd+1ef/320>
Trace; c0105866 <kernel_thread+26/30>
Trace; c01881a0 <nfsd+0/320>
Code;  c01e1687 <xfs_iget+107/150>
00000000 <_EIP>:
Code;  c01e1687 <xfs_iget+107/150>   <=====
   0:   66 83 bb 4a 01 00 00      cmpw   $0x0,0x14a(%ebx)   <=====
Code;  c01e168e <xfs_iget+10e/150>
   7:   00 
Code;  c01e168f <xfs_iget+10f/150>
   8:   75 0f                     jne    19 <_EIP+0x19> c01e16a0 <xfs_iget+120/150>
Code;  c01e1691 <xfs_iget+111/150>
   a:   66 83 a3 3c 01 00 00      andw   $0xfffffff7,0x13c(%ebx)
Code;  c01e1698 <xfs_iget+118/150>
  11:   f7 
Code;  c01e1699 <xfs_iget+119/150>
  12:   53                        push   %ebx
Code;  c01e169a <xfs_iget+11a/150>
  13:   e8 00 00 00 00            call   18 <_EIP+0x18> c01e169f <xfs_iget+11f/150>


1 warning issued.  Results may not be reliable.

--X1bOJ3K7DJ5YkBrT--