From: "Rüdiger Meier" <sweet_f_a@gmx.de>
To: linux-nfs@vger.kernel.org
Subject: infinite getdents64 loop
Date: Sat, 28 May 2011 15:02:31 +0200 [thread overview]
Message-ID: <201105281502.32719.sweet_f_a@gmx.de> (raw)
Hi,
I have some directories where I run reproducible into infinite
getdents64 loop. This happens whith kernels >=2.6.37 on clients and
just doing ls or find on that dirs.
The "broken" dirs are mostly very large with >200000 files.
While copying such dir within the underlying fs (ext4) keeps that odd
behavior it's not easy to create one on another exported filesystem.
Sometimes I could "repair" such dir by just finding the right single
file to remove. But there was nothing special with that file.
I could track down the problem to:
commit 0b26a0bf6ff398185546432420bb772bcfdf8d94
Author: Trond Myklebust <Trond.Myklebust@netapp.com>
Date: Sat Nov 20 14:26:44 2010 -0500
NFS: Ensure we return the dirent->d_type when it is known
After reverting the problem is gone.
cu,
Rudi
next reply other threads:[~2011-05-28 13:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-28 13:02 Rüdiger Meier [this message]
2011-05-28 15:00 ` infinite getdents64 loop 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
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=201105281502.32719.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).