From: Felipe Alfaro Solana <felipe_alfaro@linuxmail.org>
To: Andrew Morton <akpm@digeo.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: 2.5: NFS troubles
Date: 07 Apr 2003 10:58:53 +0200 [thread overview]
Message-ID: <1049705933.592.2.camel@teapot.felipe-alfaro.com> (raw)
In-Reply-To: <20030406171855.6bd3552d.akpm@digeo.com>
On Mon, 2003-04-07 at 02:18, Andrew Morton wrote:
> Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > The 2.5.66 ext3 code still has some issues with respect to NFS readdir
> > cookies.
>
> It might do. I have Ted's htree/NFS fixes in there though.
>
> Felipe, please do
>
> dumpe2fs /dev/hdXX | grep features
>
> if it shows dir_index then it might be an ext3 problem. If not then it is
> probably an NFS problem.
>
> If it does have dir_index set then please run
>
> tune2fs -O ^dir_index /dev/hdXX
>
> and reboot and retest.
Wonderful, Andrew... You were right. Disabling H/Tree indexes solved the
problem! Anything else?
PS: I previously solved the problem by mounting the filesystem as ext2
instead, but now it seems to be working pretty well with ext3 (at least,
I can't reproduce the hang I described in my previous message).
Thanks!
________________________________________________________________________
Linux Registered User #287198
prev parent reply other threads:[~2003-04-07 8:47 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
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 [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=1049705933.592.2.camel@teapot.felipe-alfaro.com \
--to=felipe_alfaro@linuxmail.org \
--cc=akpm@digeo.com \
--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
all inboxes | Powered by JetHome®