From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 203319] [xfstests generic/538]: unaligned direct AIO find ext4 corruption
Date: Mon, 15 Apr 2019 17:39:44 +0000 [thread overview]
Message-ID: <bug-203319-13602-sVAcn3KhTG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-203319-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=203319
--- Comment #1 from Zorro Lang (zlang@redhat.com) ---
ppc64le(64k pagesize, 512b sector size) can reproduce this bug nearly 100%. I
just ran it 200 times on pcc64le, all failed[1]. But x86_64 can't trigger this
issue, even I use 1k block size ext4.
[1]
QA output created by 538
Data verification fails
Find corruption
00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
*
00000200 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a 5a ZZZZZZZZZZZZZZZZ
00002000
FAIL: [8704, 8192, 512, 0]
-------------------------------------------------
Silence is golden
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2019-04-15 17:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 8:04 [Bug 203319] New: [xfstests generic/538]: unaligned direct AIO find ext4 corruption bugzilla-daemon
2019-04-15 17:39 ` bugzilla-daemon [this message]
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=bug-203319-13602-sVAcn3KhTG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.org \
/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).