From: David Ford <david+powerix@blue-labs.org>
To: Andrew Morton <akpm@digeo.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Trond Myklebust <trond.myklebust@fys.uio.no>,
neilb@cse.unsw.edu.au
Subject: Re: NFS problems, 2.5.5x
Date: Fri, 31 Jan 2003 18:46:53 -0800 [thread overview]
Message-ID: <3E3B351D.40208@blue-labs.org> (raw)
In-Reply-To: <20030131183059.1d37d01f.akpm@digeo.com>
Underlying filesystems on both client and server are reiserfs.
Got any more quickie suggestions? :)
Thanks,
David
Andrew Morton wrote:
>David Ford <david+powerix@blue-labs.org> wrote:
>
>
>>Synopsis: nfsserver:/home/david mount, get dir. entries loops forever,
>>2.5.59 for client and server.
>>
>>
>
>If the server is ext3+htree then you've hit the htree dir cookie bug.
>
>Use `dumpe2fs -h /dev/hda1 | grep index' to se if you're using htree.
>
>Use `tune2fs -O ^dir_index /dev/hda1' to disable it.
>
>
next prev parent reply other threads:[~2003-02-01 2:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-01 2:13 NFS problems, 2.5.5x David Ford
2003-02-01 2:30 ` Andrew Morton
2003-02-01 2:46 ` David Ford [this message]
2003-02-01 8:58 ` Trond Myklebust
2003-02-01 16:03 ` David Ford
2003-02-01 16:23 ` Trond Myklebust
2003-02-01 21:49 ` David Ford
2003-02-03 11:12 ` Oleg Drokin
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=3E3B351D.40208@blue-labs.org \
--to=david+powerix@blue-labs.org \
--cc=akpm@digeo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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