Re: nfs-client reveals MFC-if_re-probs (or vice-versa) ?
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 No. TimeSourceDestination 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.000266130.89.170.81 130.89.165.91 NFS V3 READDIR Reply (Call In 15322)[Packet size limited during capture] 15324 0.259382130.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.259788130.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.769416130.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.769749130.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.779401130.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.779780130.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.791429130.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.791857130.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.809472130.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.809816130.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] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nfs-client reveals MFC-if_re-probs (or vice-versa) ?
/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. Best regards, Arno ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: nfs-client reveals MFC-if_re-probs (or vice-versa) ?
Good morning! On Thu, Jul 27, 2006 at 09:47:42PM +0200, Arno J. Klaassen wrote: - I 'mount -o nfsv3,intr,noconn,-r=32768,-w=32768 -stable-server:/files/bsd /files/bsd ' Does nfsv3 default to TCP? If not have you tried lowering your blocksite to, say, 8192? Regards, Patrick -- punkt.de GmbH Internet - Dienstleistungen - Beratung Vorholzstr. 25Tel. 0721 9109 -0 Fax: -100 76137 Karlsruhe http://punkt.de ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
nfs-client reveals MFC-if_re-probs (or vice-versa) ?
Hello, 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) ) - though I still can 'ping -stable-server' and even 'ssh me@-stable-server-IP' - -stable-server works ok with two other -stable clients (using if_bge) and all are compiled from the very same source-base (and -stable-server works fine as well with a linux-client) which seems to exclude nfsd-probs - a kernel from June the 11th works ok - downgrading if_re.c to revision 1.46.2.14 and if_rlreg.h to revision 1.51.2.3 makes the problem disappear - this is on my demo-notebook, I can test network stuff without much limitations; I just use nfs on it for upgrading world and ports. NB, same behaviour on amd64-stable and i386-stable (multi-boot same hardware) I can fill a PR if requested or feel free to contact me for further testing. Best regards, Arno PS: relevant pciconf info : [EMAIL PROTECTED]:8:0: class=0x02 card=0x47011558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet otherwise standard kernel conf with stripped unneeded drivers and extra : device cpufreq device atapicam device sound options TCP_DROP_SYNFIN (hint??) -- Arno J. Klaassen SCITO S.A. 8 rue des Haies F-75020 Paris, France http://scito.com ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to [EMAIL PROTECTED]
