From: Jens Axboe <axboe@kernel.dk>
To: Changyu <feng_changyu@126.com>
Cc: Sitsofe Wheeler <sitsofe@gmail.com>, fio <fio@vger.kernel.org>
Subject: Re: Cannot verify dedupe data, is it a bug?
Date: Thu, 18 Oct 2018 08:31:33 -0600 [thread overview]
Message-ID: <984e4b86-eb7e-c4e2-c99f-7f794aa7aa7f@kernel.dk> (raw)
In-Reply-To: <3e72c6b8.73aa.166863f1110.Coremail.feng_changyu@126.com>
On 10/18/18 2:16 AM, Changyu wrote:
>
> Hi Jens Axboe & Sitsofe Wheeler
>
>
> Thank you very much for your help.
>
> get_io_u finally call fill_io_buffer to fill the buffer, function
> fill_io_buffer uses td->buf_state and td->buf_state_prev to generate
> duplicated data if the dedupe_percentage is set.
>
> populate_verify_io_u finally call fill_random_buf_percentage to fill
> the buffer, it use td->verify_state to generate random data.
>
As I said, I'm fine with that getting unified. The only thing to keep in
mind is that for verification data, we rely on being able to re-generate
the buffer contents, as long as we have a valid verify header. This can
be used to diagnose the nature of the corruption. As long as we retain
that property, the buffer generation for verify writes should follow the
same settings as non-verify writes.
> Should I create a issue on https://github.com/axboe/fio/issues?
Sure, probably check if it's a dupe of the issue Sitsofe referenced
first.
--
Jens Axboe
prev parent reply other threads:[~2018-10-18 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-17 12:30 Cannot verify dedupe data, is it a bug? Changyu
2018-10-17 18:32 ` Sitsofe Wheeler
2018-10-17 19:05 ` Jens Axboe
2018-10-18 8:16 ` Changyu
2018-10-18 14:31 ` Jens Axboe [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=984e4b86-eb7e-c4e2-c99f-7f794aa7aa7f@kernel.dk \
--to=axboe@kernel.dk \
--cc=feng_changyu@126.com \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.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