From: Eric Whitney <enwlinux@gmail.com>
To: linux-ext4@vger.kernel.org
Cc: tytso@mit.edu, matthew.r.wilcox@intel.com
Subject: data=journal regressions in 3.16-rc1
Date: Mon, 23 Jun 2014 16:24:04 -0400 [thread overview]
Message-ID: <20140623202404.GA16979@wallace> (raw)
My regression test results for 3.16-rc1 on x86_64 show three new xfstests
failures since 3.15 final when running on an ext4 filesystem mounted with the
data=journal and block_validity mount options (xfstests-bld's data_journal
scenario). These are generic/075, /112, and /231. All three tests fail
consistently.
These failures bisect to this kernel patch:
7fc34a62ca mm/msync.c: sync only the requested range in msync()
These failures also appear when running on 3.16-rc2, and disappear if the
aforementioned patch is reverted. I've not seen the failures in any of the
other test scenarios I've run on 3.16-rc1 (4k, ext3, nojournal, etc.).
No error messages appear in the kernel log, and not a lot useful is reported
when a test fails. Just for reference, here's the result of a generic/075
failure:
generic/075 62s ... [15:33:07] [15:33:09] [failed, exit status 1] - output mismatch (see /root/xfstests/results//generic/075.out.bad)
--- tests/generic/075.out 2014-06-16 13:14:27.233891460 -0400
+++ /root/xfstests/results//generic/075.out.bad 2014-06-23 15:33:09.654212783 -0400
@@ -4,15 +4,5 @@
-----------------------------------------------
fsx.0 : -d -N numops -S 0
-----------------------------------------------
-
------------------------------------------------
-fsx.1 : -d -N numops -S 0 -x
------------------------------------------------
...
(Run 'diff -u tests/generic/075.out /root/xfstests/results//generic/075.out.bad' to see the entire diff)
Ran: generic/075
Failures: generic/075
Failed 1 of 1 tests
And the contents of xfstests/results/generic/075.out.bad:
QA output created by 075
brevity is wit...
-----------------------------------------------
fsx.0 : -d -N numops -S 0
-----------------------------------------------
fsx (-d -N 1000 -S 0) failed, 0 - compare /root/xfstests/results//generic/075.0.{good,bad,fsxlog}
od: /root/xfstests/results//generic/075.0.fsxgood: No such file or directory
Additional test configuration info:
e2fsprogs master branch: bb9cca2ca9
xfstests master branch: 45d1fac130
Perhaps data=journal has an unexpected dependency on the old msync behavior,
given the patch comment?
Thanks,
Eric
next reply other threads:[~2014-06-23 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 20:24 Eric Whitney [this message]
2014-06-23 21:11 ` data=journal regressions in 3.16-rc1 Wilcox, Matthew R
2014-06-23 21:55 ` Eric Whitney
2014-06-26 15:12 ` Lukáš Czerner
2014-06-27 4:20 ` Namjae Jeon
2014-06-27 6:03 ` Namjae Jeon
2014-06-27 10:48 ` Lukáš Czerner
2014-06-27 11:14 ` Namjae Jeon
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=20140623202404.GA16979@wallace \
--to=enwlinux@gmail.com \
--cc=linux-ext4@vger.kernel.org \
--cc=matthew.r.wilcox@intel.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