--SkvwRMAIpAhPCcCJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Frank van der Linden <fvdl@netbsd.org> wrote:
> On Thu, Feb 09, 2006 at 01:51:47PM -0500, Jan Schaumann wrote:
> > > Maybe it has interrupt problems and does not notice the answers?
> >=20
> > Hmm, what can I do to check if that's the case, and what if it is?
>=20
> Try using tcpdump with "-s 1500 -vv". See if the file offset for the
> read requests is actually increasing. If it's not, then it's just
> retrying the same read, so it did not see the reply.

Here's a dump with the verbose output:

http://www.cs.stevens.edu/~jschauma/netbsd/dump.2

[...]
15:40:37.661692 172.16.4.1.2049 > 172.16.4.30.1980: reply ok 1124 read
REG 100755 ids 0/0 sz 3103601nlink 1 rdev 5bcf48 fsid 1300 fileid 164
249 a/m/ctime 1139511924.611207 1139511924.631211 1139512113.974079 (ttl
64, id 56003, len 1152)
15:40:37.661886 172.16.4.30.1981 > 172.16.4.1.2049: 104 read fh
19,0/1931 1024 bytes @ 3098136 (ttl 20, id 2017, len 132)
15:40:37.661928 172.16.4.1.2049 > 172.16.4.30.1981: reply ok 1124 read
REG 100755 ids 0/0 sz 3103601nlink 1 rdev 5bcf48 fsid 1300 fileid 164
249 a/m/ctime 1139511924.611207 1139511924.631211 1139512113.974079 (ttl
64, id 56006, len 1152)
15:40:37.662127 172.16.4.30.1982 > 172.16.4.1.2049: 104 read fh
19,0/1931 1024 bytes @ 3099160 (ttl 20, id 2018, len 132)
15:40:37.662171 172.16.4.1.2049 > 172.16.4.30.1982: reply ok 1124 read
REG 100755 ids 0/0 sz 3103601nlink 1 rdev 5bcf48 fsid 1300 fileid 164
249 a/m/ctime 1139511924.611207 1139511924.631211 1139512113.974079 (ttl
64, id 56009, len 1152)
15:40:37.662365 172.16.4.30.1983 > 172.16.4.1.2049: 104 read fh
19,0/1931 1024 bytes @ 3100184 (ttl 20, id 2019, len 132)
15:40:37.662418 172.16.4.1.2049 > 172.16.4.30.1983: reply ok 1124 read
REG 100755 ids 0/0 sz 3103601nlink 1 rdev 5bcf48 fsid 1300 fileid 164
249 a/m/ctime 1139511924.611207 1139511924.631211 1139512113.974079 (ttl
64, id 56012, len 1152)
15:40:37.662613 172.16.4.30.1984 > 172.16.4.1.2049: 104 read fh
19,0/1931 1024 bytes @ 3101208 (ttl 20, id 2020, len 132)
15:40:37.662662 172.16.4.1.2049 > 172.16.4.30.1984: reply ok 1124 read
REG 100755 ids 0/0 sz 3103601nlink 1 rdev 5bcf48 fsid 1300 fileid 164
249 a/m/ctime 1139511924.611207 1139511924.631211
[...]

If I interpret this correctly, then the read request is in fact not
increasing.

-Jan

--=20
The Internet interprets censorship as damage and routes around it.
	-- John Gilmore

--SkvwRMAIpAhPCcCJ
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (NetBSD)

iD8DBQFD85Q/fFtkr68iakwRAiDNAKCmgPBr/JpBeOM/KNueUpiAtt/BrgCfYSWA
MCFLFH+NKdRbUMU8daOnuw0=
=Q9Jw
-----END PGP SIGNATURE-----

--SkvwRMAIpAhPCcCJ--