Date: Fri, 2 Apr 2004 15:57:45 -0600 From: Dan Nelson <dnelson@allantgroup.com> To: Sean McNeil <sean@mcneil.com> Cc: freebsd-current@freebsd.org Subject: Re: nfs server issues Message-ID: <20040402215745.GB49311@dan.emsphone.com> In-Reply-To: <1080940409.3711.1.camel@server.mcneil.com> References: <1080882894.5980.26.camel@server.mcneil.com> <20040402163353.GC6724@dan.emsphone.com> <1080940409.3711.1.camel@server.mcneil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In the last episode (Apr 02), Sean McNeil said: > On Fri, 2004-04-02 at 08:33, Dan Nelson wrote: > > "tcpdump -s0" output might help here, I think. Do it from both > > machines and make sure no packets are being dropped, and then check > > to see what NFS request the client is trying to make that isn't > > getting processed. > > OK, here is a tcpdump. It is confusing. It looks like after the > first fragment is received it is looking up some bazaar IP > address.... > > 13:02:57.566952 free.mcneil.com.1360032988 > server.mcneil.com.nfs: 136 readdir fh 1002,54097/7890231 4096 bytes @ 0x000000000 (DF) > 13:02:57.567266 server.mcneil.com.nfs > free.mcneil.com.1360032988: reply ok 1472 readdir (frag 1645:1480@0+) > 13:02:57.567268 0.0.0.1 > 0.0.10.7: (frag 1645:4@1480) > 13:03:01.766943 arp who-has server.mcneil.com tell free.mcneil.com > 13:03:01.767040 arp reply server.mcneil.com is-at 0:d:61:27:4d:6b Weird. Is this at the server or the client? -- Dan Nelson dnelson@allantgroup.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040402215745.GB49311>