From: Dave Jones <davej@codemonkey.org.uk>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Daniel Pittman <daniel@rimspace.net>, linux-kernel@vger.kernel.org
Subject: Re: Linux <-> Linux NFS issues.
Date: Fri, 21 Mar 2003 12:57:46 +0000 [thread overview]
Message-ID: <20030321125719.GA30102@suse.de> (raw)
In-Reply-To: <shs1y103mrr.fsf@charged.uio.no>
On Fri, Mar 21, 2003 at 01:52:08PM +0100, Trond Myklebust wrote:
> Are you seeing bogus packets from both the 2.5.x client and the
> server, or is it just the server (or just the client)?
> It could also be interesting to find out if this is a UDP only
> problem, or if it occurs with TCP too...
To be honest, I've forgotten what the exact issues were.
I'll rerun some tests this afternoon, and post the results.
>From what I do recall, it was fairly simple to trigger,
an fsx run made 'bad shit' happen within a minute or two.
Dave
prev parent reply other threads:[~2003-03-21 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-21 10:37 Linux <-> Linux NFS issues Daniel Pittman
2003-03-21 12:32 ` Dave Jones
2003-03-21 12:52 ` Trond Myklebust
2003-03-21 12:57 ` Dave Jones [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=20030321125719.GA30102@suse.de \
--to=davej@codemonkey.org.uk \
--cc=daniel@rimspace.net \
--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