* odd kernel-nfs-server messages
@ 2007-11-07 4:21 Narayan Desai
2007-11-07 4:56 ` Neil Brown
0 siblings, 1 reply; 2+ messages in thread
From: Narayan Desai @ 2007-11-07 4:21 UTC (permalink / raw)
To: nfs
We are running into some kernel nfs server errors that we are having
trouble deciphering.
We are running a x86_64 nfs server. The server is running ubuntu
feisty, with their 2.6.20-16-generic kernel.
The clients are also running linux (2.6.15 kernel; we are waiting on
the system vendor to finish their port to a newer kernel) on mips64.
Under fairly heavy load (400-800 clients, not a ton of reads and
writes) we get the following messages:
[1724467.119033] RPC: bad TCP reclen 0x337e08af (large)
[1738771.833213] RPC: bad TCP reclen 0x00000014 (non-terminal)
[1738801.224098] RPC: bad TCP reclen 0x6d346e31 (non-terminal)
[1738965.738860] RPC: bad TCP reclen 0x6d376e39 (non-terminal)
[1739183.459936] RPC: bad TCP reclen 0x342e7363 (non-terminal)
[1739295.006403] RPC: bad TCP reclen 0x73797374 (non-terminal)
[1739383.784788] RPC: bad TCP reclen 0x00000003 (non-terminal)
[1739554.244212] RPC: bad TCP reclen 0x00000001 (non-terminal)
[1740372.230510] RPC: bad TCP reclen 0x3f010080 (non-terminal)
[1740573.448297] RPC: bad TCP reclen 0x79737465 (non-terminal)
[1740692.060794] RPC: bad TCP reclen 0x08190080 (large)
[1740695.795910] RPC: bad TCP reclen 0x656d0000 (non-terminal)
[1741125.251753] RPC: bad TCP reclen 0x000186a3 (non-terminal)
[1741135.467912] RPC: bad TCP reclen 0x00000002 (non-terminal)
[1741138.612606] RPC: bad TCP reclen 0x3f010080 (non-terminal)
[1741170.087073] RPC: bad TCP reclen 0x00000000 (non-terminal)
[1741529.390769] RPC: bad TCP reclen 0x20202049 (non-terminal)
[1741765.178189] rpc-srv/tcp: nfsd: sent only 12420 when sending 32900 bytes - shutting down socket
[1741929.170146] rpc-srv/tcp: nfsd: sent only 4228 when sending 32900 bytes - shutting down socket
[1741929.170162] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1741929.172954] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1741929.172983] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1741993.882718] rpc-srv/tcp: nfsd: sent only 24708 when sending 32900 bytes - shutting down socket
[1741993.882733] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1741993.882750] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743013.356969] rpc-srv/tcp: nfsd: sent only 20612 when sending 32900 bytes - shutting down socket
[1743013.356990] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743013.357007] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743132.799893] RPC: bad TCP reclen 0x20312e35 (non-terminal)
[1743156.085226] RPC: bad TCP reclen 0x302e3030 (non-terminal)
[1743178.527927] RPC: bad TCP reclen 0x30452b30 (non-terminal)
[1743302.061768] RPC: bad TCP reclen 0x30303030 (non-terminal)
[1743325.774782] rpc-srv/tcp: nfsd: sent only 25496 when sending 32900 bytes - shutting down socket
[1743325.776326] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743332.191913] RPC: bad TCP reclen 0x30303020 (non-terminal)
[1743396.683214] rpc-srv/tcp: nfsd: sent only 16516 when sending 32900 bytes - shutting down socket
[1743400.329696] rpc-srv/tcp: nfsd: sent only 12420 when sending 32900 bytes - shutting down socket
[1743400.329715] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743400.329741] rpc-srv/tcp: nfsd: got error -32 when sending 32900 bytes - shutting down socket
[1743415.486338] rpc-srv/tcp: nfsd: sent only 24708 when sending 32900 bytes - shutting down socket
[1743421.714057] svc: bad direction -2147483528, dropping request
[1743421.763703] RPC: bad TCP reclen 0x001a8000 (non-terminal)
[1743465.969286] rpc-srv/tcp: nfsd: sent only 20612 when sending 32900 bytes - shutting down socket
[1743470.886759] rpc-srv/tcp: nfsd: sent only 16516 when sending 32900 bytes - shutting down socket
The system is on the other side of a gigabit attached gateway, and we
are only seeing between 20-30 mbps of traffic through the
gateway. Also, we are mounting the filesystem with tcp,hard,intr.
Can anyone explain what is going on here?
Thanks in advance.
-nld
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: odd kernel-nfs-server messages
2007-11-07 4:21 odd kernel-nfs-server messages Narayan Desai
@ 2007-11-07 4:56 ` Neil Brown
0 siblings, 0 replies; 2+ messages in thread
From: Neil Brown @ 2007-11-07 4:56 UTC (permalink / raw)
To: Narayan Desai; +Cc: nfs
On Tuesday November 6, desai@mcs.anl.gov wrote:
> We are running into some kernel nfs server errors that we are having
> trouble deciphering.
>
> We are running a x86_64 nfs server. The server is running ubuntu
> feisty, with their 2.6.20-16-generic kernel.
>
> The clients are also running linux (2.6.15 kernel; we are waiting on
> the system vendor to finish their port to a newer kernel) on mips64.
This looks a lot like the bug fixed by commit
e0ab53deaa91293a7958d63d5a2cf4c5645ad6f0
which was still present in 2.6.15 (fix in 2.6.18).
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=e0ab53deaa91293a7958d63d5a2cf4c5645ad6f0
If the client gets an error sending data (because there is no buffer
space), the remainder of the packet is discard, but it keeps the same
tcp connection open. When it sends another packet, presumably when
buffer space is available, it gets sent and appears to be part of the
previous packet. Confusion ensues.
NeilBrown
>
> Under fairly heavy load (400-800 clients, not a ton of reads and
> writes) we get the following messages:
>
> [1724467.119033] RPC: bad TCP reclen 0x337e08af (large)
> [1738771.833213] RPC: bad TCP reclen 0x00000014 (non-terminal)
> [1738801.224098] RPC: bad TCP reclen 0x6d346e31 (non-terminal)
> [1738965.738860] RPC: bad TCP reclen 0x6d376e39 (non-terminal)
> [1739183.459936] RPC: bad TCP reclen 0x342e7363 (non-terminal)
> [1739295.006403] RPC: bad TCP reclen 0x73797374 (non-terminal)
> [1739383.784788] RPC: bad TCP reclen 0x00000003 (non-terminal)
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2007-11-07 4:56 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-11-07 4:21 odd kernel-nfs-server messages Narayan Desai
2007-11-07 4:56 ` Neil Brown
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.