xfs
[Top] [All Lists]

Re: XFS and knfsd

To: Ajay Shekhawat <ajay@xxxxxxxxxxxxxxxxx>
Subject: Re: XFS and knfsd
From: Steve Lord <lord@xxxxxxx>
Date: Tue, 10 Apr 2001 10:33:49 -0500
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: Message from Ajay Shekhawat <ajay@xxxxxxxxxxxxxxxxx> of "Tue, 10 Apr 2001 11:04:13 EDT." <20010410110413.S16131@xxxxxxxxxxxxxxxxxxxxxxxx>
Sender: owner-linux-xfs@xxxxxxxxxxx
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. 

I am currently working another nfs bug which only shows visible manifestation
on solaris clients, but appears to be bad packet generation on a readdir.


> 
> Are there any tricks to getting knfsd working with XFS? Our server which
> serves an XFS partition gets an "oops" after about 15 hours of extremely
> heavy use. I'm using the latest distro from CVS (2.4.3-XFS).  Here's the
> kdb output of the oops, just in case someone has any ideas on how to
> debug this:
> 
> Unable to handle kernel NULL pointer dereference at virtual address 00000000
>  printing eip:
> c0145933
> *pde = 00000000
> 
> Entering kdb (current=0xceffc000, pid 625) on processor 0 Oops: Oops
> due to oops @ 0xc0145933
> eax = 0xcff9ae70 ebx = 0xffffffe8 ecx = 0x0000000f edx = 0xcff80000 
> esi = 0x00000000 edi = 0xceffdeb4 esp = 0xceffde48 eip = 0xc0145933 
> ebp = 0xceffde68 xss = 0x00000018 xcs = 0x00000010 eflags = 0x00010207 
> xds = 0xcff80018 xes = 0x00000018 origeax = 0xffffffff &regs = 0xceffde14
> [0]kdb> bt
>     EBP       EIP         Function(args)
> 0xceffde68 0xc0145933 d_lookup+0x67 (0xc83e70c0, 0xceffdeb4)
>                                kernel .text 0xc0100000 0xc01458cc 0xc01459e8
> 0xceffde7c 0xc013c911 cached_lookup+0x11 (0xc83e70c0, 0xceffdeb4, 0x0)
>                                kernel .text 0xc0100000 0xc013c900 0xc013c954
> 0xceffdea0 0xc013d862 lookup_hash+0x52 (0xceffdeb4, 0xc83e70c0)
>                                kernel .text 0xc0100000 0xc013d810 0xc013d914
> 0xceffdec0 0xc013d969 lookup_one+0x55 (0xc4b860e0, 0xc83e70c0)
>                                kernel .text 0xc0100000 0xc013d914 0xc013d97c
> 0xceffdf04 0xc016d882 nfsd_lookup+0x3b2 (0xcf05ac00, 0xcf05aa00, 0xc4b860e0, 
> 0x6, 0xcf05a800)
>                                kernel .text 0xc0100000 0xc016d4d0 0xc016d9cc
> 0xceffdf2c 0xc016b50b nfsd_proc_lookup+0x87 (0xcf05ac00, 0xcf05aa00, 0xcf05a8
> 00)
>                                kernel .text 0xc0100000 0xc016b484 0xc016b520
> 0xceffdf4c 0xc016adf9 nfsd_dispatch+0xc5 (0xcf05ac00, 0xceff8014)
>                                kernel .text 0xc0100000 0xc016ad34 0xc016ae90
> 0xceffdfa8 0xc0293bca svc_process+0x2ca (0xcfef5b20, 0xcf05ac00)
>                                kernel .text 0xc0100000 0xc0293900 0xc0293e30
> 0xceffdfec 0xc016abba nfsd+0x1a2
>                                kernel .text 0xc0100000 0xc016aa18 0xc016ad34
>            0xc0105547 kernel_thread+0x23
>                                kernel .text 0xc0100000 0xc0105524 0xc010555c
> 
> 
> Any help is appreciated.
> 
> Ajay



<Prev in Thread] Current Thread [Next in Thread>