From owner-freebsd-questions Wed Jan 13 11:58:17 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA16433 for freebsd-questions-outgoing; Wed, 13 Jan 1999 11:58:17 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from gamma.qmw.ac.uk (gamma.qmw.ac.uk [138.37.6.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA16409 for ; Wed, 13 Jan 1999 11:58:14 -0800 (PST) (envelope-from scott@dcs.qmw.ac.uk) Received: from hotpoint.dcs.qmw.ac.uk by gamma.qmw.ac.uk with SMTP-QMW with ESMTP; Wed, 13 Jan 1999 13:56:31 +0000 Received: from brunos-sun.dcs.qmw.ac.uk [138.37.88.185]; by hotpoint.dcs.qmw.ac.uk (8.8.7/8.8.5/S-4.0) with SMTP; for ""; id NAA06624; Wed, 13 Jan 1999 13:54:47 GMT Received: locally by brunos-sun (SMI-8.6/QMW-client-3.2b); for "freebsd-questions@FreeBSD.ORG"; poster "scott"; id NAA01387; Wed, 13 Jan 1999 13:52:37 GMT Message-ID: <19990113135237.C993@dcs.qmw.ac.uk> Date: Wed, 13 Jan 1999 13:52:37 +0000 From: Scott Mitchell To: freebsd-questions@FreeBSD.ORG Subject: NFS mount failures -- HELP! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, all you gurus, this one has everybody around here stumped: The story so far -- one small FreeBSD server, running 2.2.7R and configured much like everything else around here (NIS, everything mounted by amd using some *very* hairy maps). Working just great until last Friday, when it suddently started refusing to mount anything from one particular file server. The timing co-incides with the installation of a new switch with something of a nanny syndrome; it likes to throw away over-long UDP packets and those with bad checksums. In general our amd maps mount things using UDP with (I think) a 8K block size. I now can't mount anything from the offending server over UDP, even wfter reducing the block size to 1K. TCP mounts work fine, but I can't force those to be used without messing with the (shared) amd maps or hacking on amd itself. The problem appears to be limited to servers that route through the new switch to get to my client, but I'm not 100% sure on that point. Other machines (Linux, IRIX) on the same network as the client have no problems. I haven't changed any configuration on the client for several months, and it was working perfectly until this started. The obvious culprit is the switch, but that doesn't explain why only this pair of machines is affected (the server runs FreeBSD also, BTW). I've attached the packet trace result from one such failed mount attempt (chorus is the client, hotpoint the server) Nobody here can figure out exactly what's causing this, so any suggestions will be most welcome. Many TIA, Scott Script started on Mon Jan 11 11:17:43 1999 chorus# tcpdump host hotpoint and host chorus tcpdump: listening on ed0 11:18:44.016706 chorus.12000000 > hotpoint.dcs.qmw.ac.uk.nfs: 40 null 11:18:44.017297 hotpoint.dcs.qmw.ac.uk.nfs > chorus.12000000: reply ok 24 11:18:44.024125 chorus.1021 > hotpoint.dcs.qmw.ac.uk.sunrpc: udp 100 11:18:44.024751 hotpoint.dcs.qmw.ac.uk.sunrpc > chorus.1021: udp 28 11:18:44.035510 chorus.1021 > hotpoint.dcs.qmw.ac.uk.1017: udp 100 11:18:44.036147 hotpoint.dcs.qmw.ac.uk.1017 > chorus.1021: udp 32 11:18:44.038803 chorus.1021 > hotpoint.dcs.qmw.ac.uk.sunrpc: udp 100 11:18:44.039374 hotpoint.dcs.qmw.ac.uk.sunrpc > chorus.1021: udp 28 11:18:44.039588 chorus.1021 > hotpoint.dcs.qmw.ac.uk.1017: udp 100 11:18:44.041504 hotpoint.dcs.qmw.ac.uk.1017 > chorus.1021: udp 60 11:18:44.104319 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:18:44.105054 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:18:44.105595 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable 11:18:45.110380 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:18:45.111358 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:18:45.111784 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable 11:18:47.120343 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:18:47.121140 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:18:47.121564 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable 11:18:51.130341 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:18:51.131076 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:18:51.131488 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable 11:18:59.140395 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:18:59.141117 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:18:59.141584 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable 11:19:14.040729 chorus.22000000 > hotpoint.dcs.qmw.ac.uk.nfs: 40 null 11:19:14.041309 hotpoint.dcs.qmw.ac.uk.nfs > chorus.22000000: reply ok 24 11:19:15.150341 chorus.9dd92009 > hotpoint.dcs.qmw.ac.uk.nfs: 92 getattr [|nfs] 11:19:15.151137 hotpoint.dcs.qmw.ac.uk.nfs > chorus.9dd92009: reply ok 96 11:19:15.151567 chorus > hotpoint.dcs.qmw.ac.uk: icmp: chorus udp port 1035 unreachable ^C 274 packets received by filter 0 packets dropped by kernel chorus# exit Script done on Mon Jan 11 11:19:48 1999 -- =========================================================================== Scott Mitchell | PGP Key ID |"If I can't have my coffee, I'm just | 0x54B171B9 | like a dried up piece of roast goat" QMW College, London, UK | 0xAA775B8B | -- J. S. Bach. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message