On Tue, Apr 10, 2001 at 10:33:49AM -0500, Steve Lord wrote:
> We are aware of your problem, can you fill in a few more details such as
> are you running nfs v2 or v3 exports and what do you characterize as
> very heavy load, nfsstat output might be interesting after a few hours of
> uptime. Client quantities and types would be good to.
Here's the latest oops:
Unable to handle kernel paging request at virtual address 373a2e68
printing eip:
c013d363
*pde = 00000000
Entering kdb (current=0xc82ca000, pid 4728) on processor 0 Oops: Oops
due to oops @ 0xc013d363
eax = 0x373a2e40 ebx = 0xcf105aa0 ecx = 0x00000001 edx = 0xcf92df00
esi = 0x00000000 edi = 0xcf1030e0 esp = 0xc82cbf04 eip = 0xc013d363
ebp = 0xc82cbf28 xss = 0x00000018 xcs = 0x00000010 eflags = 0x00010202
xds = 0xcf920018 xes = 0x00000018 origeax = 0xffffffff ®s = 0xc82cbed0
and here's the output from the last nfsstat -s :
04/11/01 01:02:19 Server rpc stats:
calls badcalls badauth badclnt xdrcall
21379580 0 0 0 0
Server nfs v2:
null getattr setattr root lookup readlink
0 0% 161 0% 0 0% 0 0% 129603 0% 0 0%
read wrcache write create remove rename
16108111 75% 0 0% 5061861 23% 39886 0% 39957 0% 0 0%
link symlink mkdir rmdir readdir fsstat
0 0% 0 0% 0 0% 0 0% 1 0% 0 0%
Server nfs v3:
null getattr setattr lookup access readlink
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
read write create mkdir symlink mknod
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
remove rmdir rename link readdir readdirplus
0 0% 0 0% 0 0% 0 0% 0 0% 0 0%
fsstat fsinfo pathconf commit
0 0% 0 0% 0 0% 0 0%
pagebuf 1405636 921281 484366 295 2 24162 1471597 44205
Ajay
|