From: "Rüdiger Meier" <sweet_f_a@gmx.de>
To: linux-nfs@vger.kernel.org
Subject: Re: infinite getdents64 loop
Date: Tue, 31 May 2011 11:47:24 +0200 [thread overview]
Message-ID: <201105311147.24939.sweet_f_a@gmx.de> (raw)
In-Reply-To: <1306767521.5971.2.camel@lade.trondhjem.org>
On Monday 30 May 2011, Trond Myklebust wrote:
> On Mon, 2011-05-30 at 11:37 +0200, Ruediger Meier wrote:
> >
> > Does this mean ext4 generally does not work with for nfs?
>
> ext2/3/4 are all known to have this problem when you switch on the
> hashed b-tree directories. Typically, a directory with a million
> entries will have several tens of cookie collisions.
Ok, like Jeff mentioned in the other reply disabling dir_index solves
it.
I wish I had seen this documented somewhere before switching from xfs to
ext4 but it's not easy to find something about these ext4/nfs probs
without knowing the details already.
Ext4 being default file system on many distros made me feel safe.
thanks for helping,
Rudi
next prev parent reply other threads:[~2011-05-31 9:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 13:02 infinite getdents64 loop Rüdiger Meier
2011-05-28 15:00 ` Rüdiger Meier
2011-05-29 16:05 ` Trond Myklebust
2011-05-29 16:55 ` Rüdiger Meier
2011-05-29 17:04 ` Trond Myklebust
[not found] ` <1306688643.2386.24.camel-SyLVLa/KEI9HwK5hSS5vWB2eb7JE58TQ@public.gmane.org>
2011-05-30 9:37 ` Ruediger Meier
2011-05-30 11:59 ` Jeff Layton
2011-05-30 12:42 ` Ruediger Meier
2011-05-30 14:58 ` Trond Myklebust
2011-05-31 9:47 ` Rüdiger Meier [this message]
2011-05-31 10:18 ` Bernd Schubert
2011-05-31 12:35 ` Ted Ts'o
2011-05-31 17:07 ` Bernd Schubert
2011-05-31 17:13 ` Boaz Harrosh
2011-05-31 17:30 ` Bernd Schubert
2011-06-01 13:10 ` Boaz Harrosh
2011-06-01 16:15 ` Trond Myklebust
2011-05-31 17:26 ` Andreas Dilger
2011-05-31 17:43 ` Bernd Schubert
2011-05-31 19:16 ` Andreas Dilger
2011-05-31 14:51 ` Bryan Schumaker
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=201105311147.24939.sweet_f_a@gmx.de \
--to=sweet_f_a@gmx.de \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).