public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Ankit Kumar <ankit.kumar@samsung.com>, axboe@kernel.dk
Cc: fio@vger.kernel.org,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
	john.g.garry@oracle.com
Subject: Re: [PATCH 00/21] verify fixes and a new test suite
Date: Thu, 27 Feb 2025 11:54:48 -0500	[thread overview]
Message-ID: <35bee198-cb20-4a29-9960-075c510819d3@gmail.com> (raw)
In-Reply-To: <20250227104727.1794982-1-ankit.kumar@samsung.com>

On 2/27/25 5:47 AM, Ankit Kumar wrote:
> This series fixes few issues with verify, and introduces a new test
> suite.
> 
> Inital few patches add the missing client/server support for
> verify_write_sequence. This also changes its behavior such that if
> verify_write_sequence is explicitly enabled fio will not disable it
> under any circumstance.
> 
> Numerous header seed mismatch issues have been reported. This series
> introduces a new option verify_header_seed which is similar to
> verify_write_sequence, which allow users to disable any header seed
> verification. For certain workloads which used to overwrite header seed
> before verification, we simply disable the header seed checks now. This
> now includes a few more scenarios such as verify_only mode, read only
> workloads and workloads with norandommap, where the header seed match is
> not guaranteed.
> 
> Few more fixes related to verify_offset, workloads that have offset
> modifiers, verification issue when multiple files are specified, are part
> of this series.
> 
> Lastly this includes robust test suite for verify.
> CI run result: https://github.com/vincentkfu/fio/actions/runs/13552248490
> 
> Note: The fixes in this series doesn't cover experimental_verify and any
> workload with variable block sizes.
> 

I have worked closely with Ankit on these patches and hope others can 
take a look to point out anything we may have missed.

Vincent

  parent reply	other threads:[~2025-02-27 16:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20250227053350epcas5p31b3b5b47590d70804dade59842d87b27@epcas5p3.samsung.com>
2025-02-27 10:47 ` [PATCH 00/21] verify fixes and a new test suite Ankit Kumar
2025-02-27  7:28   ` fiotestbot
2025-02-27 10:47   ` [PATCH 01/21] filesetup: remove unnecessary check Ankit Kumar
2025-02-27 10:47   ` [PATCH 02/21] verify: add missing client/server support for verify_write_sequence Ankit Kumar
2025-02-27 10:47   ` [PATCH 03/21] init: write sequence behavior change for verify_only mode Ankit Kumar
2025-02-27 10:47   ` [PATCH 04/21] fio: add verify_header_seed option Ankit Kumar
2025-02-27 10:47   ` [PATCH 05/21] verify: disable header seed checking instead of overwriting it Ankit Kumar
2025-02-27 10:47   ` [PATCH 06/21] verify: enable header seed check for 100% write jobs Ankit Kumar
2025-02-27 10:47   ` [PATCH 07/21] verify: disable header seed check for verify_only jobs Ankit Kumar
2025-02-27 10:47   ` [PATCH 08/21] verify: header seed check for read only workloads Ankit Kumar
2025-02-27 10:47   ` [PATCH 09/21] verify: fix verify issues with norandommap Ankit Kumar
2025-02-27 10:47   ` [PATCH 10/21] verify: disable write sequence checks with norandommap and iodepth > 1 Ankit Kumar
2025-02-27 10:47   ` [PATCH 11/21] backend: fix verify issue during readwrite Ankit Kumar
2025-02-27 10:47   ` [PATCH 12/21] init: fixup verify_offset option Ankit Kumar
2025-02-27 10:47   ` [PATCH 13/21] verify: fix verify issue with offest modifiers Ankit Kumar
2025-02-27 10:47   ` [PATCH 14/21] verify: adjust fio_offset_overlap_risk to include randommap Ankit Kumar
2025-02-27 10:47   ` [PATCH 15/21] t/fiotestcommon: do not require nvmecdev argument for Requirements Ankit Kumar
2025-02-27 10:47   ` [PATCH 16/21] t/fiotestlib: improve JSON decoding Ankit Kumar
2025-02-27 10:47   ` [PATCH 17/21] t/fiotestlib: display stderr size when it is not empty but should be Ankit Kumar
2025-02-27 10:47   ` [PATCH 18/21] t/verify.py: Add verify test script Ankit Kumar
2025-02-27 10:47   ` [PATCH 19/21] t/fiotestcommon: add a success pattern for long tests Ankit Kumar
2025-02-27 10:47   ` [PATCH 20/21] t/run-fio-test: add t/verify.py Ankit Kumar
2025-02-27 10:47   ` [PATCH 21/21] ci: add nightly test for verify Ankit Kumar
2025-02-27 16:54   ` Vincent Fu [this message]
2025-03-05 12:36     ` [PATCH 00/21] verify fixes and a new test suite Shinichiro Kawasaki
2025-03-06 19:13       ` Vincent Fu

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=35bee198-cb20-4a29-9960-075c510819d3@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=ankit.kumar@samsung.com \
    --cc=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=john.g.garry@oracle.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