From: Zheng Liu <gnehzuil.liu@gmail.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Theodore Ts'o <tytso@mit.edu>, linux-ext4 <linux-ext4@vger.kernel.org>
Subject: Re: A couple of ext4 crashes with inlinedata/bigalloc
Date: Tue, 8 Apr 2014 19:54:25 +0800 [thread overview]
Message-ID: <20140408115425.GA23781@gmail.com> (raw)
In-Reply-To: <20140311030604.GK9875@birch.djwong.org>
On Mon, Mar 10, 2014 at 08:06:04PM -0700, Darrick J. Wong wrote:
> Hi all,
>
> A couple of errors to complain about before I send out the e2fsprogs patchbomb.
> :)
>
> Zheng: I've been running the metadata checksum test with inline_data set.
> flat_dir_test is a stress test which copies /usr/share/doc into a filesystem
> and then "enlarges" the directories by recursively renaming "$foo" to
> "$foo.longer", with the results below. e2fsck complained that the directories
> involved (4156, 4251) have multiple links to the subdir inode. I'm not sure
> what this is all about; the only (circumstantial) evidence I have is that it
> goes away if I don't turn on inline_data.
Hi Darrick,
I guess that you were talking about this bug at LSF/MM submmit this
year, right? Thanks for reporting this bug. I am trying to take a
closer look at it. It would be great if you could tell me where I can
find the your test program ('flat_dir_test').
Regards,
- Zheng
next prev parent reply other threads:[~2014-04-08 11:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 3:06 A couple of ext4 crashes with inlinedata/bigalloc Darrick J. Wong
2014-03-11 6:25 ` Darrick J. Wong
2014-04-08 11:54 ` Zheng Liu [this message]
2014-04-08 18:40 ` Darrick J. Wong
2014-04-09 4:56 ` Zheng Liu
2014-04-09 18:04 ` Darrick J. Wong
2014-08-25 19:09 ` Darrick J. Wong
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=20140408115425.GA23781@gmail.com \
--to=gnehzuil.liu@gmail.com \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
/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).