mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Ext2 devel <ext2-devel@lists.sourceforge.net>,
	NFS maillist <nfs@lists.sourceforge.net>,
	Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [NFS] htree+NFS (NFS client bug?)
Date: 27 Nov 2002 00:58:42 -0800	[thread overview]
Message-ID: <1038387522.31021.188.camel@ixodes.goop.org> (raw)
In-Reply-To: <shsptsrd761.fsf@charged.uio.no>

[-- Attachment #1: Type: text/plain, Size: 888 bytes --]

On Tue, 2002-11-26 at 19:26, Trond Myklebust wrote:
> >>>>> " " == Jeremy Fitzhardinge <jeremy@goop.org> writes:
> 
>      > It looks to me like some sort of problem managing the NFS
>      > readdir cookies, but it isn't clear to me whether this is the
>      > NFS server/ext3 generating bad cookies, or the NFS client
>      > handling them wrongly.
> 
> In order to determine which of the two needs to be fixed, it would
> help if you could print out the cookies from that listing or better
> still: if you could provide us with the raw tcpdump output. Please
> remember to use an 8k snaplen for the tcpdump...

Here's a pcap dump file of the transaction.  I changed [rw]size to 1024
because I couldn't work out how to get ethereal to reassemble the
fragments.  It doesn't seem to have affected the behaviour at all.

This was with a 2.5.47 client (same server as before).

        J

[-- Attachment #2: nfs-htree.pcap.gz --]
[-- Type: application/x-gzip, Size: 2318 bytes --]

  parent reply	other threads:[~2002-11-27  8:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-26 23:44 Jeremy Fitzhardinge
2002-11-27  3:26 ` [NFS] " Trond Myklebust
2002-11-27  2:59   ` [Ext2-devel] " chrisl
2002-11-27  8:58   ` Jeremy Fitzhardinge [this message]
2002-11-27 15:00     ` Stephen C. Tweedie
2002-11-27 20:25       ` Trond Myklebust
2002-11-27 20:55         ` Stephen C. Tweedie
2002-11-27 22:44           ` Trond Myklebust
2002-11-28 16:41             ` Stephen C. Tweedie
2002-11-28 16:58               ` Trond Myklebust
2002-11-28 17:09                 ` Stephen C. Tweedie
2002-11-28 17:57                   ` Trond Myklebust
2002-11-28 16:44           ` Stephen C. Tweedie
2002-11-28 17:13             ` Stephen C. Tweedie
2002-11-28 17:44               ` Trond Myklebust
2002-11-28 20:00               ` Jeremy Fitzhardinge
2002-11-28  2:07       ` Jeremy Fitzhardinge
2002-11-28  2:46         ` Trond Myklebust
2002-11-27 13:33 ` Theodore Ts'o
2002-11-27 20:42   ` Trond Myklebust

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=1038387522.31021.188.camel@ixodes.goop.org \
    --to=jeremy@goop.org \
    --cc=ext2-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --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

all inboxes | Powered by JetHome®