All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sitsofe Wheeler <sitsofe@gmail.com>
To: Peter Sabaini <peter@sabaini.at>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Fio verify crc32 fault
Date: Fri, 4 Dec 2020 14:41:44 +0000	[thread overview]
Message-ID: <CALjAwxipZXaJ9z3WVJoukR=tt8OikcKDHDa5uCxuWQS_Y0Toag@mail.gmail.com> (raw)
In-Reply-To: <0de8d04b-bcaa-415a-4587-c5bd7f674079@sabaini.at>

Hi,

On Thu, 3 Dec 2020 at 17:27, Peter Sabaini <peter@sabaini.at> wrote:
>
> Hey,
>
> I've got a fio verify run on an NVMe that gives me a crc32 verification fault, however it's not reproducible -- when rerunning on the same NVMe it comes back fine.
>
> Also I'm getting a funny "error=Invalid or incomplete multibyte or wide character" error reported, see below.
>
> Any hints for this?
>
> Many thanks,
> peter.
>
> Test output
>
> Running command: sudo -n fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=fio_test_verify --bs=4M --iodepth=64 --size=95% --verify=crc32c-intel --runtime=7200s --filename=/dev/nvme0n1 --readwrite=randwrite
>
> fio_test_verify: (g=0): rw=randwrite, bs=4M-4M/4M-4M/4M-4M, ioengine=libaio, iodepth=64
> fio-2.2.10

^^^ Your fio is VERY old... Does the same thing happen with a recent
fio (see https://github.com/axboe/fio/releases for what we're up to)?

-- 
Sitsofe | http://sucs.org/~sits/


  reply	other threads:[~2020-12-04 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-03 17:23 Fio verify crc32 fault Peter Sabaini
2020-12-04 14:41 ` Sitsofe Wheeler [this message]
2020-12-04 17:01   ` Jeff Furlong
2020-12-05 17:09     ` Peter Sabaini

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='CALjAwxipZXaJ9z3WVJoukR=tt8OikcKDHDa5uCxuWQS_Y0Toag@mail.gmail.com' \
    --to=sitsofe@gmail.com \
    --cc=fio@vger.kernel.org \
    --cc=peter@sabaini.at \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.