nfsd oops with 2.6.5-rc2-mm4
Quoted 3 lines · Frank
I got a reproducible oops after a few minutes with a 2.6.5-rc2-mm4 kernel.
...
[<c01e6a8d>]nfsd_readdir+0x69/0xe8
was some exported directory quite big? Try running a "find /mnt/..." on the client to see when exactly it fails. I observe similar behavior when reading huge directories of some 1000 entries. What nfs version are you using? You may try "mount -o nfsvers=2 ..." or 3.
My own Oops seems to be reproducible when using a Sun (2.8) as client, only. It did not occur when using nfsV2. I also failed to reproduce the bug when mounting by an other Linux client. So may be we observe two different bugs here.
With that instability observed, I won't/can't switch to 2.6.x for my system in production :-( Can I help somehow? Making a TCP-dump? Try some patches?
Dieter.
Signature · 4 lines
Dieter Stüken, con terra GmbH, Münster
[email protected]
http://www.conterra.de/
(0)251-7474-501Quoted 1 line · Dieter Stueken
was some exported directory quite big?
Yes, some exported directories contains a lot of small files.
Quoted 2 lines
What nfs version
are you using? You may try "mount -o nfsvers=2 ..." or 3.
Version 3. I can give version 2 a try but there will probably a significant loss of performance :(
Quoted 2 lines
My own Oops seems to be reproducible when using a Sun (2.8) as client, only.
There actually 10 clients, 9 are Linux 2.6.2-rc2-mm2, 1 is indeed a Solaris 2.8 box.
Quoted 2 lines
It did not occur when using nfsV2. I also failed to reproduce the bug when mounting by an other Linux client.
Unfortunately this is a production environment and I can hardly switch the Solaris box off in order to make it sure that it is triggering the bug.
Quoted 1 line
So may be we observe two different bugs here.
Your situation looks similar.
I reverted to 2.6.2-rc2-mm3, the server didn't crash after 6 hours. Crossing fingers...
Quoted 1 line · Frank Denis
I reverted to 2.6.2-rc2-mm3, the server didn't crash after 6 hours. Crossing fingers...
Pointless.
2.6.2-rc2-mm3 just crashed the same way.
Unable to handle kernel NULL pointer dereference at virtual address 00000004 printing eip: c029fb79 *pde = 00000000 Oops: 0002 [#1] SMP CPU: 0 EIP: 0060:[<c029fb79>] Not tainted VLI EFLAGS: 00010287 (2.6.5-rc2-mm3)
EIP is at do_tcp_sendpages+0x197/0xa79
eax: f5b75108 ebx: f42c0980 ecx: 00000008 edx: 00000000
esi: 00000001 edi: f5b75100 ebp: f61bddec esp: f62c5e34
ds: 007b es: 007b ss: 0068
Process nfsd (pid: 3325, threadinfo=f62c5000 task=f7727670)
Stack: 000000d0 000000d0 f62c5e60 00000000 15270000 c01e6991 f5b75110 f61bdc64
00000008 00000000 00000000 00000000 000005b4 00007530 00000000
f61bdc00
00000008 00000000 c02a04e3 f61bdc00 f62c5eac 00000000 00000008
00000000
Call Trace:
[<c01e6991>] nfsd_readdir+0x69/0xe8
[<c02a04e3>] tcp_sendpage+0x88/0x96
[<c02d8ccd>] svc_sendto+0x16a/0x29e
[<c01ecfd9>] encode_post_op_attr+0x1c9/0x241
[<c02d9d39>] svc_tcp_sendto+0x53/0xa8
[<c02da4f1>] svc_send+0xb9/0xfc
[<c02dc17c>] svcauth_unix_release+0x57/0x59
[<c02d8189>] svc_process+0x184/0x60e
[<c02e2d9c>] common_interrupt+0x18/0x20
[<c01e0ce9>] nfsd+0x1ea/0x3b6
[<c01e0aff>] nfsd+0x0/0x3b6
[<c0104e01>] kernel_thread_helper+0x5/0xb