--pgp-sign-Multipart_Fri_Sep_16_21:01:50_2005-1
Content-Type: text/plain; charset=US-ASCII

After switching from 2.0_RC2 to 3.0_BETA, I find the NFS client seems
to be broken:

20:59:34.776804 69.31.131.61.2643938620 > 192.168.1.124.2049: 100 getattr fh 32,123/795200 (ttl 64, id 65170, len 128)
                         4500 0080 fe92 0000 4011 f159 451f 833d
                         c0a8 017c 03ea 0801 006c e00c 9d97 4d3c
                         0000 0000 0000 0002 0001 86a3 0000 0003
                         0000 0001 0000 0001 0000 0018 0000 0000
                         0000 0000 0000 0000 0000 0000 0000 0001
                         0000 0000 0000 0000 0000 0000 0000 0020
                         0080 007b 0000 0002 000a 0000 000c 2240
                         640c 827d 000a 0000 0000 0002 39f4 d307
20:59:34.777872 192.168.1.124.2049 > 69.31.131.61.2643938620: reply ok 112 getattr REG 644 ids 0/207 sz 0x3b10f6 (DF) (ttl 254, id 58284, len 140)
                         4500 008c e3ac 4000 fe11 0e33 c0a8 017c
                         451f 833d 0801 03ea 0078 f04e 9d97 4d3c
                         0000 0001 0000 0000 0000 0000 0000 0000
                         0000 0000 0000 0000 0000 0001 0000 01a4
                         0000 0001 0000 0000 0000 00cf 0000 0000
                         003b 10f6 0000 0000 003b 4000 0000 0000
                         0000 0000 0000 0020 0000 007b 0000 0000
                         000c 2240 432b 2316 015a dce0 432b 63e5
                         2684 1b80 432b 63e5 2684 1b80
21:00:34.777644 69.31.131.61.2643938621 > 192.168.1.124.2049: 100 getattr fh 32,123/795200 (ttl 64, id 65221, len 128)
                         4500 0080 fec5 0000 4011 f126 451f 833d
                         c0a8 017c 03ea 0801 006c e00b 9d97 4d3d
                         0000 0000 0000 0002 0001 86a3 0000 0003
                         0000 0001 0000 0001 0000 0018 0000 0000
                         0000 0000 0000 0000 0000 0000 0000 0001
                         0000 0000 0000 0000 0000 0000 0000 0020
                         0080 007b 0000 0002 000a 0000 000c 2240
                         640c 827d 000a 0000 0000 0002 39f4 d307
21:00:34.778814 192.168.1.124.2049 > 69.31.131.61.2643938621: reply ok 112 getattr REG 644 ids 0/207 sz 0x3b10f6 (DF) (ttl 254, id 58285, len 140)
                         4500 008c e3ad 4000 fe11 0e32 c0a8 017c
                         451f 833d 0801 03ea 0078 f04d 9d97 4d3d
                         0000 0001 0000 0000 0000 0000 0000 0000
                         0000 0000 0000 0000 0000 0001 0000 01a4
                         0000 0001 0000 0000 0000 00cf 0000 0000
                         003b 10f6 0000 0000 003b 4000 0000 0000
                         0000 0000 0000 0020 0000 007b 0000 0000
                         000c 2240 432b 2316 015a dce0 432b 63e5
                         2684 1b80 432b 63e5 2684 1b80

It's been doing this for about half an hour, but it worked ok for
several hours before that.  The NFS server is Solaris 10.

IIRC I had the same problem with 2.0 if I used NFS over IPv6, but over
v4 it worked well enough to build four releases and copy many
gigabytes.  Now, apparently not.  Is there anyone working on NFS that
would like tcpdump captures of this, or some other type of debugging?

--pgp-sign-Multipart_Fri_Sep_16_21:01:50_2005-1
Content-Type: application/pgp-signature
Content-Transfer-Encoding: 7bit

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

iQCVAwUAQytrConCBbTaW/4dAQJ7OgQAsYt4rEeOlAOCrw3JNl3ylKQaY39zLeMT
G7Rcq8DwFJefTeUVDQW2zNmk0flBQdI/bGcMUzADAU2fpFinGx+jtIa5wG50ZExf
+hQAmC3+lJoBVhSnWqaLGYdkf/ZxX6YXmGd++VX6g0dpYhFPuM1mP/M0yG9whiz+
AQC+bzXVCe0=
=FK98
-----END PGP SIGNATURE-----

--pgp-sign-Multipart_Fri_Sep_16_21:01:50_2005-1--