public inbox for fio@vger.kernel.org
 help / color / mirror / Atom feed
From: Vincent Fu <vincentfu@gmail.com>
To: Jens Axboe <axboe@kernel.dk>,
	fio@vger.kernel.org,
	Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH v2 0/8] zbd: support continue_on_error for zonemode=zbd
Date: Wed, 7 May 2025 13:19:34 -0400	[thread overview]
Message-ID: <d120fd1e-22e3-46f4-88a6-559f256e20c5@gmail.com> (raw)
In-Reply-To: <174661736206.1785376.17260834205270367848.b4-ty@kernel.dk>

On 5/7/25 7:29 AM, Jens Axboe wrote:
> 
> On Fri, 25 Apr 2025 14:21:40 +0900, Shin'ichiro Kawasaki wrote:
>> When the continue_on_error options is specified, it is expected that the
>> workload continues to run when non-critical errors happen. However,
>> write workloads with zonemode=zbd option can not continue after errors,
>> if the failed writes cause partial data write on the target device. This
>> partial write creates write pointer gap between the device and fio, then
>> the next write requests by fio will fail due to unaligned write command
>> errors. This restriction results in undesirable test stops during long
>> runs for SMR drives which can recover defect sectors.
>>
>> [...]
> 
> Applied, thanks!
> 
> [1/8] oslib: blkzoned: add blkzoned_move_zone_wp() helper function
>        commit: 4175f4dbec5d1d9e5e0490026e98b1806188e098
> [2/8] ioengine: add move_zone_wp() callback
>        commit: 6f635d6f72ad3d4ae76fff63671a208c27bdaf2d
> [3/8] engines/libzbc: implement move_zone_wp callback
>        commit: d4f6fa5e35d6bd20dd648b3aaaad84a0a9a4fa6e
> [4/8] zbd: introduce zbd_move_zone_wp()
>        commit: 143aaff963694ee3745c204f414e1e27a759a7df
> [5/8] zbd: add the recover_zbd_write_error option
>        commit: 650c4ad385cf7ff320cb34f76784ca63d2daa32e
> [6/8] t/zbd: set badblocks related parameters in run-tests-against-nullb
>        commit: 5cbd1644e0dcfeb55e6cb4717259778ed11cc70e
> [7/8] t/zbd: add the test cases to confirm continue_on_error option
>        commit: b6002e78926bce20bc168d02c83b7c8f5dd37470
> [8/8] t/zbd: add run-tests-against-scsi_debug
>        commit: 4dc6c8da6ed938f12a42f167839100ab551ae8d1
> 
> Best regards,

Shin'ichiro, there are some build failures with macOS and Windows:

https://github.com/axboe/fio/actions/runs/14882253382

Vincent

  reply	other threads:[~2025-05-07 17:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-25  5:21 [PATCH v2 0/8] zbd: support continue_on_error for zonemode=zbd Shin'ichiro Kawasaki
2025-04-25  5:21 ` [PATCH v2 1/8] oslib: blkzoned: add blkzoned_move_zone_wp() helper function Shin'ichiro Kawasaki
2025-05-07  7:35   ` Damien Le Moal
2025-04-25  5:21 ` [PATCH v2 2/8] ioengine: add move_zone_wp() callback Shin'ichiro Kawasaki
2025-05-07  7:36   ` Damien Le Moal
2025-04-25  5:21 ` [PATCH v2 3/8] engines/libzbc: implement move_zone_wp callback Shin'ichiro Kawasaki
2025-05-07  7:41   ` Damien Le Moal
2025-04-25  5:21 ` [PATCH v2 4/8] zbd: introduce zbd_move_zone_wp() Shin'ichiro Kawasaki
2025-05-07  7:43   ` Damien Le Moal
2025-04-25  5:21 ` [PATCH v2 5/8] zbd: add the recover_zbd_write_error option Shin'ichiro Kawasaki
2025-05-07  7:48   ` Damien Le Moal
2025-04-25  5:21 ` [PATCH v2 6/8] t/zbd: set badblocks related parameters in run-tests-against-nullb Shin'ichiro Kawasaki
2025-04-25  5:21 ` [PATCH v2 7/8] t/zbd: add the test cases to confirm continue_on_error option Shin'ichiro Kawasaki
2025-04-25  5:21 ` [PATCH v2 8/8] t/zbd: add run-tests-against-scsi_debug Shin'ichiro Kawasaki
2025-05-07 11:29 ` [PATCH v2 0/8] zbd: support continue_on_error for zonemode=zbd Jens Axboe
2025-05-07 17:19   ` Vincent Fu [this message]
2025-05-07 17:22     ` Jens Axboe
2025-05-08  1:28       ` Shinichiro Kawasaki
2025-05-08 17:18         ` 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=d120fd1e-22e3-46f4-88a6-559f256e20c5@gmail.com \
    --to=vincentfu@gmail.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=fio@vger.kernel.org \
    --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