Martin Knoblauch wrote:
>> At 10:20 AM 5/14/2007, Martin Knoblauch wrote:
>>> not sure whether I should feel stupid. Inspecting the tcpdump log
>>> (snippet attached), I see a lot of "reply ERR 1448" packets coming 
> from
>>> the Sun. Which of course could explain a few things.
>> Can you turn up the tcpdump reporting to show more NFS layer decoding?
>> The "1448" is just the packet length at this level (which is a bit odd
> 
>> in
>> itself - why such a large reply?), not the error code.
> Hi Tom,
> 
>  How to turn NFS reporting up? "-vvv" does not give any more info?

Ensure that tcpdump is capturing whole frames.  By default it captures 
only 96 bytes of each Ethernet frame, which isn't enough to tell what is 
going on at the RPC or NFS layer.  Use:

   tcpdump -s0 -w/tmp/raw

to collect your data, then use WireShark, as Tom suggested to analyze 
the captured trace.