From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu
Subject: possible dev branch regression - xfstest 285/1k
Date: Fri, 15 Mar 2013 18:28:18 -0400 [thread overview]
Message-ID: <20130315222818.GA16100@wallace> (raw)
I'm seeing Xfstest 285 consistently fail for the 1k test case using the
latest dev branch while running on both x86 and ARM. Subtest 08 is
the problem. From the test output:
08. Test file with unwritten extents, only have unwritten pages
08.01 SEEK_HOLE expected 0 or 4194304, got 11264. FAIL
08.02 SEEK_HOLE expected 1 or 4194304, got 11264. FAIL
08.03 SEEK_DATA expected 10240 or 10240, got 0. FAIL
08.04 SEEK_DATA expected 10240 or 10240, got 1. FAIL
>From previous discussions, we expect 285 to fail in the ext3 (nodelalloc,
no flex_bg, and no extents) test case, but in subtest 07. It still does
that.
In the dev branch, reverting 4f42f80a8f - "ext4: use s_extent_max_zeroout_kb
value as number of kb" - results in success for 285 in the 1k test case.
Regards,
Eric
next reply other threads:[~2013-03-15 22:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-15 22:28 Eric Whitney [this message]
2013-03-16 2:32 ` possible dev branch regression - xfstest 285/1k Zheng Liu
2013-03-16 15:09 ` Zheng Liu
2013-03-17 3:06 ` Theodore Ts'o
2013-03-17 6:13 ` Zheng Liu
2013-03-18 16:10 ` Eric Sandeen
2013-03-18 16:54 ` gnehzuil.liu
2013-03-18 17:09 ` Theodore Ts'o
2013-03-18 17:34 ` Eric Sandeen
2013-03-18 20:41 ` Ben Myers
2013-03-18 23:12 ` Dave Chinner
2013-03-19 1:40 ` Theodore Ts'o
2013-03-19 2:07 ` Dave Chinner
2013-03-19 1:47 ` Dave Chinner
2013-03-19 2:00 ` Theodore Ts'o
2013-03-19 2:22 ` Dave Chinner
2013-03-19 2:28 ` Eric Sandeen
2013-03-19 8:50 ` Lukáš Czerner
2013-03-17 3:36 ` 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=20130315222818.GA16100@wallace \
--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).