From: Eric Biggers <ebiggers3@gmail.com>
To: Roman Penyaev <roman.penyaev@profitbricks.com>
Cc: Theodore Ts'o <tytso@mit.edu>,
linux-ext4@vger.kernel.org, Eric Biggers <ebiggers@google.com>
Subject: Re: Refreshed rootfs.img for kvm-xfstests
Date: Tue, 10 Jan 2017 10:50:33 -0800 [thread overview]
Message-ID: <20170110185033.GA58743@gmail.com> (raw)
In-Reply-To: <CAJrWOzAebGpyLTJL2XsP8r4zjrbG030cLEXUVUK0t2sW8=g_Gg@mail.gmail.com>
On Tue, Jan 10, 2017 at 01:48:03PM +0100, Roman Penyaev wrote:
>
> I retested the following configurations on 69973b830859 ("Linux 4.9"):
>
> ./kvm-xfstests.sh -c nojournal ext4/301
> ./kvm-xfstests.sh -c ext3conv generic/347
> ./kvm-xfstests.sh -c adv generic/396 generic/399
> ./kvm-xfstests.sh -c data_journal generic/347
> ./kvm-xfstests.sh -c bigalloc generic/399
> ./kvm-xfstests.sh -c bigalloc_1k generic/273
>
> all of the tests from list have failed.
>
> This is not very much helpful, but at least that can be a starting
> point for bisecting.
>
> When there was a successful xfstests run at least for some of
> the configurations? Would be nice to have a "good" reference.
>
Hi Roman,
Generally these have been broken for a while, or in the case of generic/396 and
generic/399 are new tests which are exposing bugs. A few of these I was already
aware of but just haven't had time to get to:
- the failure of generic/347 in data journalling mode is intermittent
- the failure of generic/396 in "adv" mode is related to the use of the inline
data feature, apparently caused by ext4_convert_inline_data() corrupting an
empty directory
- failure of generic/399 in some configurations
If you're interested in looking into any of these failing tests and either
fixing the kernel or fixing the test as appropriate, please feel free to!
Thanks,
Eric
next prev parent reply other threads:[~2017-01-10 18:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 23:14 Refreshed rootfs.img for kvm-xfstests Theodore Ts'o
2017-01-10 3:38 ` Theodore Ts'o
2017-01-10 12:48 ` Roman Penyaev
2017-01-10 15:07 ` Roman Penyaev
2017-01-11 3:05 ` Theodore Ts'o
2017-01-10 18:50 ` Eric Biggers [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-07-17 14:05 Theodore Ts'o
2016-07-21 20:22 ` Eric Whitney
2016-07-23 15:10 ` Theodore Ts'o
2016-07-23 23:06 ` Eric Whitney
2016-07-24 8:18 ` Theodore Ts'o
2016-06-30 15:28 Theodore Ts'o
2016-07-01 15:54 ` Theodore Ts'o
2016-04-04 6:13 Theodore Ts'o
2015-10-25 21:26 Theodore Ts'o
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=20170110185033.GA58743@gmail.com \
--to=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=linux-ext4@vger.kernel.org \
--cc=roman.penyaev@profitbricks.com \
--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).