From: Eric Whitney <enwlinux@gmail.com>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Eric Whitney <enwlinux@gmail.com>, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] xfstests-bld: exclude ext4 defrag tests from unsupported configurations
Date: Thu, 11 Jun 2015 16:00:51 -0400 [thread overview]
Message-ID: <20150611200051.GA505@localhost.localdomain> (raw)
In-Reply-To: <20150610192810.GB24181@thunk.org>
I haven't tried to run generic/068 in quite a while, but do see it's passing
now. I'll close the related bugzillas. Do you know which patch fixed this?
Thanks,
Eric
* Theodore Ts'o <tytso@mit.edu>:
> On Wed, Jun 10, 2015 at 02:13:19PM -0400, Eric Whitney wrote:
> > Online defrag is not currently implemented for journaled data and
> > bigalloc ext4 file systems. The xfstests that exercise online defrag
> > do not verify that the test file system supports that feature before
> > executing, resulting in spurious test failures. (In the case of
> > ext4/307, the test reports success but actually fails because the
> > e4compact test component is ignoring failures.)
> >
> > For the time being, simply exclude these tests to eliminate the test
> > failure noise.
> >
> > Signed-off-by: Eric Whitney <enwlinux@gmail.com>
>
> Thanks, applied. BTW, I had since removed data_journal.exclude
> because generic/068 should be passing with data journalling enabled.
>
> - Ted
next prev parent reply other threads:[~2015-06-11 20:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-10 18:13 [PATCH] xfstests-bld: exclude ext4 defrag tests from unsupported configurations Eric Whitney
2015-06-10 19:28 ` Theodore Ts'o
2015-06-11 20:00 ` Eric Whitney [this message]
2015-06-12 0:24 ` Eric Whitney
2015-06-15 1:14 ` Theodore Ts'o
2015-06-15 1:23 ` [PATCH] ext4: fix race between truncate and __ext4_journalled_writepage() Theodore Ts'o
2015-06-15 12:33 ` Jan Kara
2015-06-15 13:06 ` Theodore Ts'o
2015-06-15 17:03 ` Jan Kara
2015-06-15 19:37 ` Theodore Ts'o
2015-06-15 17:59 ` Andreas Dilger
2015-06-16 12:57 ` Jan Kara
2015-06-15 20:39 ` Eric Whitney
2015-06-16 19:29 ` Eric Whitney
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=20150611200051.GA505@localhost.localdomain \
--to=enwlinux@gmail.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).