From: Zygo Blaxell <ce3g8jdj@umail.furryterror.org>
To: Chris Murphy <lists@colorremedies.com>
Cc: Andrei Borzenkov <arvidjaar@gmail.com>,
Filipe Manana <fdmanana@gmail.com>,
linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Reproducer for "compressed data + hole data corruption bug, 2018 edition" still works on 4.20.7
Date: Tue, 12 Feb 2019 17:11:07 -0500 [thread overview]
Message-ID: <20190212221107.GC23918@hungrycats.org> (raw)
In-Reply-To: <CAJCQCtT1K4RY+_nmcWZdzHVSno-ijHZYLfJz4vu-irN4p+ZYxA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4033 bytes --]
On Tue, Feb 12, 2019 at 02:48:38PM -0700, Chris Murphy wrote:
> Is it possibly related to the zlib library being used on
> Debian/Ubuntu? That you've got even one reproducer with the exact same
> hash for the transient error case means it's not hardware or random
> error; let alone two independent reproducers.
The errors are not consistent between runs. The above pattern is quite
common, but it is not the only possible output. Add in other processes
reading the 'am' file at the same time and it gets very random.
The bad data tends to have entire extents missing, replaced with zeros.
That leads to a small number of possible outputs (the choices seem to be
only to have the data or have the zeros). It does seem to be a lot more
consistent in recent (post 4.14.80) kernels, which may be interesting.
Here is an example of a diff between two copies of the 'am' file copied
while the repro script was running, filtered through hd:
# diff -u /tmp/f1 /tmp/f2
--- /tmp/f1 2019-02-12 17:05:14.861844871 -0500
+++ /tmp/f2 2019-02-12 17:05:16.883868402 -0500
@@ -56,10 +56,6 @@
*
00020000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-00021000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-00022000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
00023000 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 |................|
*
00024000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
@@ -268,10 +264,6 @@
*
000a0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-000a1000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-000a2000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
000a3000 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 |................|
*
000a4000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
@@ -688,10 +680,6 @@
*
001a0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-001a1000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-001a2000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
001a3000 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 |................|
*
001a4000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
@@ -1524,10 +1512,6 @@
*
003a0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-003a1000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-003a2000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
003a3000 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 |................|
*
003a4000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
@@ -3192,10 +3176,6 @@
*
007a0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-007a1000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-007a2000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
007a3000 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 12 |................|
*
007a4000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
@@ -5016,10 +4996,6 @@
*
00c00000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
-00c01000 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 11 |................|
-*
-00c02000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
-*
[etc...you get the idea]
I'm not sure how the zlib library is involved--sha1sum doesn't use one.
> And then what happens if you do the exact same test but change to zstd
> or lzo? No error? Strictly zlib?
Same errors on all three btrfs compression algorithms (as mentioned in
the original post from August 2018).
> --
> Chris Murphy
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2019-02-12 22:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 3:11 Reproducer for "compressed data + hole data corruption bug, 2018 editiion" Zygo Blaxell
2018-08-23 5:10 ` Qu Wenruo
2018-08-23 16:44 ` Zygo Blaxell
2018-08-23 23:50 ` Qu Wenruo
2019-02-12 3:09 ` Reproducer for "compressed data + hole data corruption bug, 2018 edition" still works on 4.20.7 Zygo Blaxell
2019-02-12 15:33 ` Christoph Anton Mitterer
2019-02-12 15:35 ` Filipe Manana
2019-02-12 17:01 ` Zygo Blaxell
2019-02-12 17:56 ` Filipe Manana
2019-02-12 18:13 ` Zygo Blaxell
2019-02-13 7:24 ` Qu Wenruo
2019-02-13 17:36 ` Filipe Manana
2019-02-13 18:14 ` Filipe Manana
2019-02-14 1:22 ` Filipe Manana
2019-02-14 5:00 ` Zygo Blaxell
2019-02-14 12:21 ` Christoph Anton Mitterer
2019-02-15 5:40 ` Zygo Blaxell
2019-03-04 15:34 ` Christoph Anton Mitterer
2019-03-07 20:07 ` Zygo Blaxell
2019-03-08 10:37 ` Filipe Manana
2019-03-14 18:58 ` Christoph Anton Mitterer
2019-03-14 20:22 ` Christoph Anton Mitterer
2019-03-14 22:39 ` Filipe Manana
2019-03-08 12:20 ` Austin S. Hemmelgarn
2019-03-14 18:58 ` Christoph Anton Mitterer
2019-03-14 18:58 ` Christoph Anton Mitterer
2019-03-15 5:28 ` Zygo Blaxell
2019-03-16 22:11 ` Christoph Anton Mitterer
2019-03-17 2:54 ` Zygo Blaxell
2019-02-15 12:02 ` Filipe Manana
2019-03-04 15:46 ` Christoph Anton Mitterer
2019-02-12 18:58 ` Andrei Borzenkov
2019-02-12 21:48 ` Chris Murphy
2019-02-12 22:11 ` Zygo Blaxell [this message]
2019-02-12 22:53 ` Chris Murphy
2019-02-13 2:46 ` Zygo Blaxell
2019-02-13 7:47 ` Roman Mamedov
2019-02-13 8:04 ` Qu Wenruo
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=20190212221107.GC23918@hungrycats.org \
--to=ce3g8jdj@umail.furryterror.org \
--cc=arvidjaar@gmail.com \
--cc=fdmanana@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=lists@colorremedies.com \
/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).