mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Kenneth Johansson <ken@canit.se>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: nfs problem 2.4.19-pre9
Date: Sun, 2 Jun 2002 12:52:25 +0200	[thread overview]
Message-ID: <15609.63721.842434.183988@charged.uio.no> (raw)
In-Reply-To: <1022962240.1186.62.camel@tiger>

>>>>> " " == Kenneth Johansson <ken@canit.se> writes:

    >> Fair enough. Have you tried a tcpdump?

     > I can send you a trace if you want. I guess you only need a
     > trace from the first stat to read fails but it has to wait an
     > hour or two it's not a good time to crash just now.

Problem is very apparent from the tcpdump: your client is only
receiving 2 or 3 out of the 6 UDP fragments in the NFS read
reply from the server. The rest is getting lost en route.

Check out the NFS FAQ on nfs.sourceforge.net. The relevant section is
the bit that asks questions of the form:

   1) Are both server and client running on the same speed network
      (i.e. are both switched 100Mbit/100Mbit or 10Mbit/10Mbit)?
   2) If you are using a switch, are you also using autonegotiation,
      or have you forced one or both of the cards (forcing is *bad*
      if your switch/hub is autonegotiating)

Cheers,
  Trond

      reply	other threads:[~2002-06-02 10:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 14:02 Kenneth Johansson
2002-06-01 19:09 ` Trond Myklebust
2002-06-01 19:39   ` Kenneth Johansson
2002-06-01 19:50     ` Trond Myklebust
2002-06-01 20:10       ` Kenneth Johansson
2002-06-02 10:52         ` Trond Myklebust [this message]

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=15609.63721.842434.183988@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=ken@canit.se \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®