Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	fio@vger.kernel.org, Jens Axboe <axboe@kernel.dk>
Cc: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
	Dmitry Fomichev <Dmitry.Fomichev@wdc.com>,
	Niklas Cassel <niklas.cassel@wdc.com>
Subject: Re: [PATCH v2 0/4] fix experimental verify
Date: Mon, 24 Oct 2022 14:26:17 -0400	[thread overview]
Message-ID: <1301e1a3-e793-7ad3-e0ad-bd3a141d1678@gmail.com> (raw)
In-Reply-To: <20221020063854.839158-1-shinichiro.kawasaki@wdc.com>

On 10/20/22 02:38, Shin'ichiro Kawasaki wrote:
> Recently I noticed that verify workload with --experimental_verify option does
> not read back verify data. I confirmed it with simple job below:
> 
>    [job]
>    filename=t0025file
>    size=128k
>    readwrite=write
>    do_verify=1
>    verify=md5
>    experimental_verify=1
> 
> Fio reported as follows. No read for verify data.
> 
>    Run status group 0 (all jobs):
>       READ: bw=0B/s (0B/s), 0B/s-0B/s (0B/s-0B/s), io=0B (0B), run=1-1msec
>       WRITE: bw=41.7MiB/s (43.7MB/s), 41.7MiB/s-41.7MiB/s (43.7MB/s-43.7MB/s)...
> 
> The debug log trace with --debug=io,verify option showed no verify data read
> either. It indicates that experimental verify is not working as expected.
> 
> This series addresses two issues to make experimental verify work again. Also
> add two test cases to confirm the issue fixes.
> 
> Of note is that this series makes test case #54 of t/zbd/test-zbd-support fail.
> I'm preparing another series to address it as well as other verify issues
> related to zonemode=zbd.
> 
> Changes from v1:
> * Reflected comments on the list to patch 3 and 4
> 
> Shin'ichiro Kawasaki (4):
>    verify: fix bytes_done accounting of experimental verify
>    verify: fix numberio accounting of experimental verify
>    test: add test for verify read back of experimental verify
>    test: add test for experimental verify with loops and time_based
>      options
> 
>   backend.c          |  8 ++++++--
>   fio.h              |  2 ++
>   io_u.c             | 23 +++++++++++++++++------
>   libfio.c           |  1 +
>   rate-submit.c      |  2 ++
>   t/jobs/t0025.fio   |  8 ++++++++
>   t/jobs/t0026.fio   | 20 ++++++++++++++++++++
>   t/run-fio-tests.py | 31 +++++++++++++++++++++++++++++++
>   verify.c           |  2 --
>   9 files changed, 87 insertions(+), 10 deletions(-)
>   create mode 100644 t/jobs/t0025.fio
>   create mode 100644 t/jobs/t0026.fio
> 

Applied. Thanks.

Vincent

      parent reply	other threads:[~2022-10-24 20:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-20  6:38 [PATCH v2 0/4] fix experimental verify Shin'ichiro Kawasaki
2022-10-20  6:38 ` [PATCH v2 1/4] verify: fix bytes_done accounting of " Shin'ichiro Kawasaki
2022-10-20  6:38 ` [PATCH v2 2/4] verify: fix numberio " Shin'ichiro Kawasaki
2022-10-20  6:38 ` [PATCH v2 3/4] test: add test for verify read back " Shin'ichiro Kawasaki
2022-10-20  6:38 ` [PATCH v2 4/4] test: add test for experimental verify with loops and time_based options Shin'ichiro Kawasaki
2022-10-24 18:26 ` Vincent Fu [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=1301e1a3-e793-7ad3-e0ad-bd3a141d1678@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=Dmitry.Fomichev@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=damien.lemoal@opensource.wdc.com \
    --cc=fio@vger.kernel.org \
    --cc=niklas.cassel@wdc.com \
    --cc=shinichiro.kawasaki@wdc.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