From: Andrew Morton <akpm@digeo.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: felipe_alfaro@linuxmail.org, linux-kernel@vger.kernel.org
Subject: Re: 2.5: NFS troubles
Date: Sun, 6 Apr 2003 17:18:55 -0700 [thread overview]
Message-ID: <20030406171855.6bd3552d.akpm@digeo.com> (raw)
In-Reply-To: <shsbrzjn5of.fsf@charged.uio.no>
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
>
> >>>>> " " == Felipe Alfaro Solana <felipe_alfaro@linuxmail.org> writes:
>
> > Hello, I'm testing 2.5.66-bk11 on my NFS server running
> > RH9. When I run the "find" command on the NFS share from my
> > client computer, it hangs forever after a while, but it always
> > hangs *exactly* at the same place every time. However, if I
> > boot into NFS with RH9's standard kernel (2.4.20), the "find"
> > command works as expected and is able to complete with any
> > hangs or delays.
>
> > My NFS server (hostname glass) has a whole ext3 partition -
> > mounted under /data - formatted as ext3.
>
> 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.
next prev parent reply other threads:[~2003-04-07 0:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-06 12:06 2.5: NFS troubles Felipe Alfaro Solana
2003-04-06 12:58 ` Trond Myklebust
2003-04-07 0:18 ` Andrew Morton [this message]
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
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=20030406171855.6bd3552d.akpm@digeo.com \
--to=akpm@digeo.com \
--cc=felipe_alfaro@linuxmail.org \
--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