der Mouse wrote:

>
>Have you tried moving the offending bytes to lower in the file but the
>same position modulo 8192 (and truncating the file size to match)?
>
Yes, I just tried that and the problem remain with this smaller file:

00000000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  
|................|
*
00001c50  00 00 00 00 00 00 00 00  00 00 f6 89 d9 ba 96 7d  
|...............}|
00001c60  37 60 43 70 e8 7d aa ba  f3 49 f0 77 80 b5 48 fe  
|7`Cp.}...I.w..H.|
00001c70  fc ac fd 01 fc 66 04 f0  be 54 74 bc ba 6d d2 8e  
|.....f...Tt..m..|
00001c80  72 dd f7 03 87 6c 3b a4  d5 e8 3f                 |r....l;...?|
00001c8b

>
>Have you tried any other NFS client on the same client hardware?
>
No, I only have NetBSD running on those (I do have a small partition 
with MacOS 9 on them as well, but I don't think it has any NFS client, 
or does it?).

>
>If you haven't verified that other software on the same hardware can
>read the file, I'd be inclined to suspect your hardware.  You say you
>have _two_ Macs; do they both exhibit identical behaviour as clients in
>this regard?  That would make it more likely it is software - or
>perhaps a bug in a particular chip rev, used in both machines.
>
Yes, we have the same problem with both Macs and they have identical 
hardware.

>
>It might be interesting to tcpdump and see if the client machine can
>receive the relevant NFS packet at all.  If so, and the contents are
>correct (compare vs a copy tcpdumped on another machine), that points
>to software; if not, that points to hardware.
>
Yes, I'll try that next.

>
>
>/~\ The ASCII				der Mouse
>\ / Ribbon Campaign
> X  Against HTML	       mouse@rodents.montreal.qc.ca
>/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B
>