<br><font size=2 face="sans-serif">Thank you! Now I do not think it is
version problem. Actually, I found that the TCP connection is never complete
between my nfs client and server. The server reply the SYN,ACK but the
client just do not respond. As for UDP is the same . I use inetd and portmap
on client side , I think there must be sth wrong on my client side.</font>
<br><font size=2 face="sans-serif">packets :</font>
<br><font size=2 face="sans-serif">from client to server:</font>
<br><font size=2 face="sans-serif">src port : 794, dest port:111</font>
<br><font size=2 face="sans-serif">from server to client:</font>
<br><font size=2 face="sans-serif">src port:111 dest port:794</font>
<br>
<br><font size=2 face="sans-serif">the tcpdump on the client side is look
like this</font>
<br>
<br><font size=2 face="sans-serif">10.25.16.160.794 > 10.25.16.130.sunrpc:
S, cksum 0x5740 (correct), 31406388</font>
<br>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x79e6 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x79e6 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 60) 10.25.16.160.794 > 10.25.16.130.sunrpc:
S, cksum 0x5614 (correct), 31406388</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x76ff (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x76ff (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x76f8 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x76f8 (correct), 2533961748:2</font>
<br>
<br>
<br><font size=2 face="sans-serif"> 60) 10.25.16.160.794 > 10.25.16.130.sunrpc:
S, cksum 0x53bc (correct), 31406388</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x7123 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x7123 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x711c (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x711c (correct), 2533961748:2</font>
<br>
<br>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x6563 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 60) 10.25.16.160.794 > 10.25.16.130.sunrpc:
S, cksum 0x4f0c (correct), 31406388</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x6561 (correct), 2533961748:2</font>
<br><font size=2 face="sans-serif"> 10.25.16.130.sunrpc > 10.25.16.160.794:
S, cksum 0x6563 (correct), 2533961748:</font>
<br>
<br><font size=2 face="sans-serif">Is it the portmap or inetd' problem?</font>
<br>
<br>
<br>
<table width=100%>
<tr valign=top>
<td width=40%><font size=1 face="sans-serif"><b>Denys Vlasenko <vda.linux@googlemail.com></b>
</font>
<p><font size=1 face="sans-serif">08/29/2007 06:37 PM</font>
<td width=59%>
<table width=100%>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">$B08@h(B</font></div>
<td><font size=1 face="sans-serif">xiao.liang@cn.alps.com</font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">cc</font></div>
<td><font size=1 face="sans-serif">busybox@busybox.net<br>
"hinko.kocevar@cetrtapot.si" <hinko.kocevar@cetrtapot.si></font>
<tr valign=top>
<td>
<div align=right><font size=1 face="sans-serif">$B7oL>(B</font></div>
<td><font size=1 face="sans-serif">Re: mount:nfsmount failed: Bad file
descriptor</font></table>
<br>
<table>
<tr valign=top>
<td>
<td></table>
<br></table>
<br>
<br>
<br><tt><font size=2>On Wednesday 29 August 2007 03:42, xiao.liang@cn.alps.com
wrote:<br>
> After I try busbox 1.6.1, the bad file descriptor error disappear,
but<br>
> still got RPC timeout error. And the mount service is still V1. I
think it<br>
<br>
Yes, strace was clearly showing that server doesn't respond.<br>
If you still unsure what's going on, use tcpdump to see<br>
what happens on the wire.<br>
<br>
(If you send tcpdump outout to the list, use attachment - linewrapped<br>
tcpdump would be totally unreadable)<br>
<br>
> is due to the failed nfs mount use a very early verion 1 of mount
service.<br>
> Anyone who knows how to update the mount servce version?<br>
<br>
busybox mount doesn't know about NFS version 1, only 2 and 3<br>
are supported.<br>
<br>
If you mean that your NFS server is version 1, well, you<br>
need to install newer one.<br>
--<br>
vda<br>
</font></tt>
<br>