mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: More fun with fsx.
Date: Mon, 17 Dec 2001 01:00:18 +0100	[thread overview]
Message-ID: <15389.13714.559348.873531@charged.uio.no> (raw)
In-Reply-To: <Pine.LNX.4.33.0112162226460.16845-100000@Appserv.suse.de>
In-Reply-To: <15389.4070.855955.296791@charged.uio.no> <Pine.LNX.4.33.0112162226460.16845-100000@Appserv.suse.de>

>>>>> " " == Dave Jones <davej@suse.de> writes:

     > On Sun, 16 Dec 2001, Trond Myklebust wrote:
    >> In that case, I'll need a tcpdump of the point at which the
    >> error occurs.

     > Sure no problem... any particular preferred options ?  Want
     > client and server, or just client ?

Client should suffice. If you could start something like

tcpdump -s 256 -w tcpdump.out

close to the point at which the error occurs, and send me the
resulting file, then that should be OK. I'm mainly out to check
whether or not the server is the one returning the EIO error, or
possibly if it is returning bad post-op attributes. Those are the only
remaining possibilities if hard mounts are being used.

BTW: could you also tell me a bit about the server? Is this an ext[23]
partition and knfsd? I'm still a bit wary of ReiserFS...

Cheers,
   Trond

  parent reply	other threads:[~2001-12-17  0:01 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-15 15:40 fsx for Linux showing up reiserfs problem? Dave Jones
2001-12-15 16:18 ` Martin Josefsson
2001-12-15 16:52 ` More fun with fsx Dave Jones
2001-12-15 17:08 ` [reiserfs-dev] fsx for Linux showing up reiserfs problem? Hans Reiser
2001-12-16 14:53 ` More fun with fsx Trond Myklebust
2001-12-16 14:58   ` Dave Jones
2001-12-16 15:26     ` Dave Jones
2001-12-16 15:39     ` Trond Myklebust
2001-12-16 15:47       ` Dave Jones
2001-12-16 15:50       ` Trond Myklebust
2001-12-16 18:48     ` Trond Myklebust
2001-12-16 20:59       ` Dave Jones
2001-12-16 21:19       ` Trond Myklebust
2001-12-16 21:34         ` Dave Jones
2001-12-17  0:00         ` Trond Myklebust [this message]
2001-12-17  1:33           ` Trond Myklebust
2001-12-17  1:37             ` Dave Jones
2001-12-17  1:47             ` Trond Myklebust
2001-12-17  1:50               ` Dave Jones
2001-12-17  2:51             ` Dave Jones
2001-12-17  9:59             ` Trond Myklebust
2001-12-17 14:30               ` Dave Jones
2001-12-17 14:41                 ` Dave Jones
2001-12-17 16:06                 ` Trond Myklebust
2001-12-17 16:15                   ` Dave Jones
2001-12-18 20:31               ` David S. Miller
2001-12-18 20:36                 ` Dave Jones
2001-12-20 15:55                   ` Nathan Straz
2001-12-20 16:02                     ` 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=15389.13714.559348.873531@charged.uio.no \
    --to=trond.myklebust@fys.uio.no \
    --cc=davej@suse.de \
    --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®