Subject: NFS server ignoring writes?
To: Brian C. Grayson <bgrayson@marvin.ece.utexas.edu>
From: Charles M. Hannum <root@ihack.net>
List: current-users
Date: 11/14/1998 01:29:07
You left out one critical bit of information: whether you gave any
other arguments to tcpdump(8). If you tell it `port foo', then only
the first fragment of an IP packet will ever be printed, because the
other fragments don't have a port number in them. If you did this,
please rerun it with arguments that will display all the fragments.
Also:
20:28:20.188513 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 145:1480@0+) (ttl 64)
20:28:22.067087 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 146:1480@0+) (ttl 64)
20:28:25.817010 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 147:1480@0+) (ttl 64)
20:28:33.307100 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 148:1480@0+) (ttl 64)
20:28:48.277230 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 149:1480@0+) (ttl 64)
20:29:18.207529 aulait.998563913 > latte.nfs: 1472 write fh 4,0/1931 8192 bytes @ 516096 <unstable> (frag 152:1480@0+) (ttl 64)
Note the IP `ID' field is increasing, and the exponential time
differences. These are not fragments from the same packet; they're
separate packets. Clearly the client is retrying.