From: Stefan Ring <stefanrin@gmail.com>
To: qemu-block@nongnu.org, qemu-devel@nongnu.org, integration@gluster.org
Subject: Re: Strange data corruption issue with gluster (libgfapi) and ZFS
Date: Thu, 27 Feb 2020 22:12:50 +0100 [thread overview]
Message-ID: <CAAxjCEx__TsY75b0iecG1a_wUO2MF2UMVP50nFHQi2Ouyu0znw@mail.gmail.com> (raw)
In-Reply-To: <CAAxjCEwv61e87ZUz-jueL9AkzaNbY3pRoFmf2dah-p9W8nosWA@mail.gmail.com>
On Tue, Feb 25, 2020 at 3:12 PM Stefan Ring <stefanrin@gmail.com> wrote:
>
> I find many instances with the following pattern:
>
> current file length (= max position + size written): p
> write request n writes from (p + hole_size), thus leaving a hole
> request n+1 writes exactly hole_size, starting from p, thus completely
> filling the hole
> The two requests' in-flight times overlap.
> hole_size can be almost any value (7-127).
Victory! I have a reproducer in the form of a plain C libgfapi client.
However, I have not been able to trigger corruption by just executing
the simple pattern in an artificial way. Currently, I need to feed my
reproducer 2 GB of data that I streamed out of the qemu block driver.
I get two possible end states out of my reproducer: The correct one or
a corrupted one, where 48 KB are zeroed out. It takes no more than 10
runs to get each of them at least once. The corrupted end state is
exactly the same that I got from the real qemu process from where I
obtained the streamed trace. This gives me a lot of confidence in the
soundness of my reproducer.
More details will follow.
next prev parent reply other threads:[~2020-02-27 21:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAxjCEzHQz4cG_8m7S6=CwCBoN5daQs+KVyuU5GL5Tq3Bky1NA@mail.gmail.com>
2020-02-24 12:35 ` Strange data corruption issue with gluster (libgfapi) and ZFS Stefan Ring
2020-02-24 13:10 ` Stefan Ring
2020-02-24 13:26 ` Kevin Wolf
2020-02-24 15:50 ` Stefan Ring
2020-02-25 14:12 ` Stefan Ring
2020-02-27 21:12 ` Stefan Ring [this message]
2020-02-27 22:25 ` Stefan Ring
2020-02-28 11:10 ` Kevin Wolf
2020-02-28 11:41 ` Stefan Ring
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=CAAxjCEx__TsY75b0iecG1a_wUO2MF2UMVP50nFHQi2Ouyu0znw@mail.gmail.com \
--to=stefanrin@gmail.com \
--cc=integration@gluster.org \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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).