The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Dave Jones <davej@codemonkey.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.60 NFS FSX
Date: Thu, 13 Feb 2003 21:30:48 +0000	[thread overview]
Message-ID: <20030213213048.GA24878@codemonkey.org.uk> (raw)
In-Reply-To: <15948.2650.639700.363495@charged.uio.no>

On Thu, Feb 13, 2003 at 10:12:58PM +0100, Trond Myklebust wrote:

 > > There seems to be some garbage at the end of the capture.  I'm
 > > not sure why, but it seems tcpdump does that sometimes.
 > Does it do that on 2.4.x? I've certainly never seen that happen on a
 > stable kernel.

I'll try in a few minutes. It doesn't always do it in 2.5, just like
once every dozen or so captures.  NIC is a 3com 3c905C-TX/TX-M [Tornado]
in the client, and an Intel 82801BA/BAM/CA/CAM in the server, both
boxes connected through a cheapo 100MB switch. Nothing special.

 > In fact ethereal reports 
 > 
 >  Message: pcap: File has 1045168887-byte packet, bigger than maximum of 65535
 > No wonder we see bizarre crashes...

That did seem odd yes.  I put it down to a tcpdump bug.
But if you think thats whats triggering it...

 > There are several other odd features in this tcpdump. Random UDP
 > packets from the server to the client with a junk payload (usually
 > consisting of a load of zeros) appear to be pretty frequent.

Wacky. Interested netdev parties can find the ~2MB tcpdump output at
http://www.codemonkey.org.uk/cruft/tcp-trond.bz2
(please don't hammer that server with requests for this unless you
 really do want/need it - the mind boggles at how many hits the nfs
 fsx dumps got in the past -- I'm sure we don't have *that* many
 interested NFS developers 8-).

 > Is this against a 2.5.x server? If so, could you try against a 2.4.x
 > or a non-linux server?

This is a 2.4.21pre3 server.  No non-linux servers to try against
right now..

		Dave

-- 
| Dave Jones.        http://www.codemonkey.org.uk
| SuSE Labs

  reply	other threads:[~2003-02-13 21:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-13 15:27 2.5.60 NFS FSX Dave Jones
2003-02-13 15:45 ` Trond Myklebust
2003-02-13 15:51   ` Dave Jones
2003-02-13 16:04     ` Trond Myklebust
2003-02-13 16:05       ` Dave Jones
2003-02-13 18:54 ` Joel Becker
2003-02-13 19:08   ` Trond Myklebust
2003-02-13 19:27     ` Dave Jones
     [not found]     ` <20030213204906.GA24109@codemonkey.org.uk>
2003-02-13 21:12       ` Trond Myklebust
2003-02-13 21:30         ` Dave Jones [this message]
2003-02-13 22:05         ` Dave Jones
2003-02-13 22:15         ` Dave Jones

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030213213048.GA24878@codemonkey.org.uk \
    --to=davej@codemonkey.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox