From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: Andreas Dilger <adilger@dilger.ca>
Cc: "linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: Strange "rm -fr" issue
Date: Mon, 30 Dec 2013 09:10:14 +0100 [thread overview]
Message-ID: <20131230081014.GA392@x4> (raw)
In-Reply-To: <59DA49F7-C44D-4C50-A9C8-55C0BB78F29C@dilger.ca>
On 2013.12.29 at 11:47 -0700, Andreas Dilger wrote:
> If you are able to reproduce this issue (extract the same tree and
> then try "rm -fr" again) please run this under strace to see how many
> entries are returned during readdir from the kernel.
>
> It could be a bug in the ext4 readdir code or it could be a bug in
> glibc or coreutils.
Unfortunately the issue is not reproducible and therefore impossible to
debug. I just thought to post it nevertheless, just to see if perhaps
someone else encounters the same problem.
--
Markus
next prev parent reply other threads:[~2013-12-30 8:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-29 14:24 Strange "rm -fr" issue Markus Trippelsdorf
2013-12-29 18:47 ` Andreas Dilger
2013-12-30 8:10 ` Markus Trippelsdorf [this message]
2013-12-30 22:17 ` Jan Kara
2013-12-30 22:22 ` Markus Trippelsdorf
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=20131230081014.GA392@x4 \
--to=markus@trippelsdorf.de \
--cc=adilger@dilger.ca \
--cc=linux-ext4@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