From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Andrew Morton <akpm@digeo.com>
Cc: rml@tech9.net, trond.myklebust@fys.uio.no,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5: NFS troubles
Date: 07 Apr 2003 11:24:44 +0200 [thread overview]
Message-ID: <1049707384.592.19.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <20030407021331.1ffbfa7f.akpm@digeo.com>
On Mon, 2003-04-07 at 11:13, Andrew Morton wrote:
> Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> wrote:
> >
> > I don't think it's a client problem, since I can't reproduce with
> > 2.4+ext3, 2.5.66+ext2 and 2.5.66+ext3-dir_index, but is reproducible
> > with 2.5.66+ext3+dir_index.
> >
>
> Well it could still be an NFS problem. Turning off htree on the server could
> cause filenames to be returned in a different order (or is that illegal?) or
> changed timing or such.
>
> If Robert is seeing it on non-htree servers then we'd need to see that fixed
> up before deciding if there is also an(other) htree bug.
>
> First thing we need to do is to debug it. Trond would have a better idea of
> how to set about that than I. Possibly a tcpdump of the traffic?
I sent a tcpdump and strace as attachments in my original message ;-)
Do you have it handy? Should I send it again?...
________________________________________________________________________
Linux Registered User #287198
next prev parent reply other threads:[~2003-04-07 9:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 12:06 Felipe Alfaro Solana
2003-04-06 12:58 ` Trond Myklebust
2003-04-07 0:18 ` Andrew Morton
2003-04-07 0:27 ` Robert Love
2003-04-07 9:01 ` Felipe Alfaro Solana
2003-04-07 9:13 ` Andrew Morton
2003-04-07 9:24 ` Felipe Alfaro Solana [this message]
2003-04-07 21:58 ` Trond Myklebust
2003-04-07 9:39 ` Trond Myklebust
2003-04-07 13:23 ` Trond Myklebust
2003-04-07 15:17 ` Robert Love
2003-04-07 8:58 ` Felipe Alfaro Solana
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=1049707384.592.19.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.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®