Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Chao Guo <guochao@nutstore.net>, fio@vger.kernel.org
Subject: Re: [Bug-Report] fio cannot handle some situation
Date: Tue, 21 Aug 2018 09:19:57 -0600	[thread overview]
Message-ID: <b0ba9833-7739-e9ea-0b36-e8744734c9ed@kernel.dk> (raw)
In-Reply-To: <CADhrBQRs9AnEwucJi01ydagqZjuZ=CYeWKeBG+Ds0P46sb-g+Q@mail.gmail.com>

On 8/21/18 4:21 AM, Chao Guo wrote:
> 1) A description of what you think the bug is:
> 
>   when using readwrite=randread and do_verify=1, fio always fails with
> 'Invalid or incomplete multibyte or wide character'
> 
> 
> 2) Environment (Linux distro version, kernel version). This is mostly
>    needed if it's a build bug.
> 
>    CentOS 7(fio 3.1-2)
> 
>    CentOS 7(build from github.com/axboe/fio, master)
> 
>    Ubuntu 18.04(fio 3.1-1)
> 
> 3) The output from fio --version.
> 
>    See above
> 
> 4) How to reproduce. Please include a full list of the parameters
>    passed to fio and the job file used (if any).
> 
> [global]
> ioengine=libaio
> direct=1
> group_reporting
> iodepth=128
> bs=1M
> readwrite=randread
> size=500MB
> do_verify=1
> verify=crc32c-intel
> 
> [test]
> filename=test

You're asking fio to verify a file, which assumes that the file
has already been written with verify data. That's not the case
(unless you ran another job to do that first), so the verify will
naturally fail.

Change your readwrite=randread to readwrite=randwrite, and fio
will randomly write it first, them randomly read and verify.

-- 
Jens Axboe



  reply	other threads:[~2018-08-21 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 10:21 [Bug-Report] fio cannot handle some situation Chao Guo
2018-08-21 15:19 ` Jens Axboe [this message]
2018-08-22 10:40   ` Chao Guo
2018-08-22 15:09     ` Jens Axboe
2018-08-23  2:58       ` Chao Guo
2018-08-23  3:00       ` Chao Guo
2018-08-23  5:46       ` Chao Guo
2018-08-23  5:50       ` Chao Guo
2018-08-23  5:56       ` Chao Guo

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=b0ba9833-7739-e9ea-0b36-e8744734c9ed@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=guochao@nutstore.net \
    /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