Date: Mon, 31 Jul 2006 21:15:27 +0200 From: Pieter de Goeje <pieter@degoeje.nl> To: "Arno J. Klaassen" <arno@heho.snv.jussieu.fr> Cc: freebsd-stable@freebsd.org Subject: Re: nfs-client reveals MFC-if_re-probs (or vice-versa) ? Message-ID: <200607312115.27386.pieter@degoeje.nl> In-Reply-To: <wpmzasutd3.fsf@heho.labo> References: <wpr706q17l.fsf@heho.labo> <wpmzasutd3.fsf@heho.labo>
next in thread | previous in thread | raw e-mail | index | archive | help
--Boundary-00=_PblzEqDKRjQWJou Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline On Saturday 29 July 2006 21:02, Arno J. Klaassen wrote: > /me wrote: > > I have a curious problem which at first sight seems related to the > > end-June MFC of if_re : > > > > - I 'mount -o nfsv3,intr,noconn,-r=32768,-w=32768 > > <-stable-server>:/files/bsd /files/bsd ' > > > > - (/usr/ports and /usr/src are symlinks to /files/bsd/*) quickly > > after a portinstall/portversion etc. I get : > > nfs server <-stable-server>: not responding > > (and the corresponding process stuck in 'bo_wwa' according to > > top(1) ) > > for info: #define RE_CSUM_FEATURES 0 in otherwise up to date if_re.c > solves the problem. I was having the same problem with my if_re card (RealTek 8169S). As a workaround I changed the nic. I'll give your solution a try. Using tcpdump I found that the NFS server was actually sending the right(?) packets (dump attached) but the client was somehow ignoring them... - Pieter --Boundary-00=_PblzEqDKRjQWJou Content-Type: text/plain; charset="iso-8859-1"; name="re_nfs" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="re_nfs" No. Time Source Destination Protocol Info 15322 *REF* 130.89.165.91 130.89.170.81 NFS V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15323 0.000266 130.89.170.81 130.89.165.91 NFS V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15324 0.259382 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15325 0.259788 130.89.170.81 130.89.165.91 NFS [RPC duplicate of #15323]V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15326 0.769416 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15327 0.769749 130.89.170.81 130.89.165.91 NFS [RPC duplicate of #15323]V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15328 1.779401 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15329 1.779780 130.89.170.81 130.89.165.91 NFS [RPC duplicate of #15323]V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15330 3.791429 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15331 3.791857 130.89.170.81 130.89.165.91 NFS [RPC duplicate of #15323]V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15332 7.809472 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] 15333 7.809816 130.89.170.81 130.89.165.91 NFS [RPC duplicate of #15323]V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15334 15.835566 130.89.165.91 130.89.170.81 NFS [RPC retransmission of #15322]V3 READDIR Call (Reply In 15323)[Packet size limited during capture] --Boundary-00=_PblzEqDKRjQWJou--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200607312115.27386.pieter>