From: Michal Simek <monstr-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
To: linux-nfs@vger.kernel.org
Subject: NFS-UDP retransmission error
Date: Wed, 29 Oct 2008 13:12:44 +0100 [thread overview]
Message-ID: <4908533C.7060808@monstr.eu> (raw)
[-- Attachment #1: Type: text/plain, Size: 4777 bytes --]
Hi all,
I am working with 2.6.20 kernel for Microblaze CPU.
We have two kernel variants for MMU and noMMU kernel in the same repo.
I am solving problem which we have with NFS.
My board is connected to router and then to my pc (100Mb/s local network)
On noMMU kernel I have no problem to mount nfs via tcp or udp. I tested version
2 or version 3 and there is no problem there.
On MMU kernel I have no problem with TCP connection.
UDP is failing there.
I have found on http://nfs.sourceforge.net/ any setting which could help but the
result is the same. Portmap (nolock) usage has no impact for it. Mount is from
busybox.
Below are some error log and more details.
Do you have any suggestion what could be wrong?
Thanks for your help,
Michal Simek
Here is the error log:
~ # mount -t nfs -o udp -o nolock -o
rsize=2048,wsize=2048,timeo=30,retrans=10,vers=2 192.168.0.102:/tftpboot/nfs /mnt
nfs: server 192.168.0.102 not responding, timed out
mount: Mounting 192.168.0.102:/tftpboot/nfs on /mnt failed: Input/output error
~ # mount -t nfs -o udp -o nolock -o
rsize=2048,wsize=2048,timeo=30,retrans=10,vers=3 192.168.0.102:/tftpboot/nfs /mnt
nfs: server 192.168.0.102 not responding, timed out
mount: Mounting 192.168.0.102:/tftpboot/nfs on /mnt failed: Input/output error
>From ethereal output I have got
15 0.074022 192.168.0.10 192.168.0.102 MOUNT V3 MNT Call /tftpboot/nfs
16 0.077197 192.168.0.102 192.168.0.10 MOUNT V3 MNT Reply (Call In 15)
17 0.090271 192.168.0.10 192.168.0.102 Portmap V2 GETPORT Call NFS(100003) V:3 UDP
18 0.090427 192.168.0.102 192.168.0.10 Portmap V2 GETPORT Reply (Call In 17)
Port:2049
19 0.116142 192.168.0.10 192.168.0.102 NFS V3 NULL Call
20 0.116195 192.168.0.102 192.168.0.10 NFS V3 NULL Reply (Call In 19)
21 2.512284 192.168.0.10 192.168.0.102 NFS [RPC retransmission of #19]V3 NULL
Call (Reply In 20)
22 2.512375 192.168.0.102 192.168.0.10 NFS [RPC duplicate of #20]V3 NULL Reply
(Call In 19)23 7.312308 192.168.0.10 192.168.0.102 NFS [RPC retransmission of
#19]V3 NULL Call (Reply In 20)
24 7.312411 192.168.0.102 192.168.0.10 NFS [RPC duplicate of #20]V3 NULL Reply
(Call In 19)
25 16.912231 192.168.0.10 192.168.0.102 NFS [RPC retransmission of #19]V3 NULL
Call (Reply In 20)
26 16.942211 192.168.0.102 192.168.0.10 NFS [RPC duplicate of #20]V3 NULL Reply
(Call In 19)
27 36.112152 192.168.0.10 192.168.0.102 NFS [RPC retransmission of #19]V3 NULL
Call (Reply In 20)
28 36.112249 192.168.0.102 192.168.0.10 NFS [RPC duplicate of #20]V3 NULL Reply
(Call In 19)
~ # cat /proc/net/rpc/nfs
net 0 0 0 0
rpc 1 4 0
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc4 35 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
~ #
Correct behavior on noMMU kernel.
15 0.069978 192.168.0.10 192.168.0.102 MOUNT V3 MNT Call /tftpboot/nfs
16 0.073372 192.168.0.102 192.168.0.10 MOUNT V3 MNT Reply (Call In 15)
17 0.078076 192.168.0.10 192.168.0.102 Portmap V2 GETPORT Call NFS(100003) V:3 UDP
18 0.078156 192.168.0.102 192.168.0.10 Portmap V2 GETPORT Reply (Call In 17)
Port:2049
19 0.087533 192.168.0.10 192.168.0.102 NFS V3 NULL Call
20 0.087585 192.168.0.102 192.168.0.10 NFS V3 NULL Reply (Call In 19)
21 0.112497 192.168.0.10 192.168.0.102 NFSACL V3 NULL Call
22 0.112563 192.168.0.102 192.168.0.10 NFSACL V3 NULL Reply (Call In 21)
23 0.115845 192.168.0.10 192.168.0.102 NFS V3 FSINFO Call, FH:0xf307ed0f
24 0.115896 192.168.0.102 192.168.0.10 NFS V3 FSINFO Reply (Call In 23)
25 0.119220 192.168.0.10 192.168.0.102 NFS V3 GETATTR Call, FH:0xf307ed0f
26 0.119266 192.168.0.102 192.168.0.10 NFS V3 GETATTR Reply (Call In 25)
Directory mode:0775 uid:504 gid:504
27 0.123107 192.168.0.10 192.168.0.102 NFS V3 FSINFO Call, FH:0xf307ed0f
28 0.123156 192.168.0.102 192.168.0.10 NFS V3 FSINFO Reply (Call In 27)
29 0.126442 192.168.0.10 192.168.0.102 NFS V3 GETATTR Call, FH:0xf307ed0f
30 0.126487 192.168.0.102 192.168.0.10 NFS V3 GETATTR Reply (Call In 29)
Directory mode:0775 uid:504 gid:504
# cat /proc/net/rpc/nfs
net 0 0 0 0
rpc 5 0 0
proc2 18 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
proc3 22 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0
proc4 35 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Ethereal output is in attachment.
Kernel .config networking part
#
# Network File Systems
#
CONFIG_NFS_FS=y
CONFIG_NFS_V3=y
CONFIG_NFS_V3_ACL=y
CONFIG_NFS_V4=y
# CONFIG_NFS_DIRECTIO is not set
CONFIG_NFSD=y
CONFIG_NFSD_V2_ACL=y
CONFIG_NFSD_V3=y
CONFIG_NFSD_V3_ACL=y
CONFIG_NFSD_V4=y
CONFIG_NFSD_TCP=y
CONFIG_LOCKD=y
CONFIG_LOCKD_V4=y
CONFIG_EXPORTFS=y
CONFIG_NFS_ACL_SUPPORT=y
CONFIG_NFS_COMMON=y
CONFIG_SUNRPC=y
CONFIG_SUNRPC_GSS=y
CONFIG_RPCSEC_GSS_KRB5=y
CONFIG_RPCSEC_GSS_SPKM3=y
CONFIG_SMB_FS=y
# CONFIG_SMB_NLS_DEFAULT is not set
[-- Attachment #2: mmu-udp-failed2 --]
[-- Type: application/octet-stream, Size: 2816 bytes --]
[-- Attachment #3: nommu --]
[-- Type: application/octet-stream, Size: 3774 bytes --]
reply other threads:[~2008-10-29 12:41 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4908533C.7060808@monstr.eu \
--to=monstr-psz03upnqpehxe+lvdladg@public.gmane.org \
--cc=linux-nfs@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox