From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>, fio@vger.kernel.org
Subject: Re: Spurious verification mismatch?
Date: Thu, 07 Aug 2014 15:27:26 -0600 [thread overview]
Message-ID: <53E3EF3E.8090204@kernel.dk> (raw)
In-Reply-To: <CALjAwxgC_7JRais+2ahfotYbJQ2ENwgE8KvnBF+2htPfVYEtvA@mail.gmail.com>
On 08/05/2014 09:22 AM, Sitsofe Wheeler wrote:
> When trying to use fio from git
> ae7e055f755e77dfa71ae9040250ce8eec238721 (commit dated July 25th) the
> following line always fails at the same point:
>
> ./fio --randseed=1 --ioengine=libaio --iodepth=1 --bs=64k
> --rw=randwrite --verify=meta --verify_backlog=50 --filename
> /dev/shm/foo --size=8M --time_based --runtime=1m --name=go
>
> go: (g=0): rw=randwrite, bs=64K-64K/64K-64K/64K-64K, ioengine=libaio, iodepth=1
> fio-2.1.11-10-gae7e
> Starting 1 process
> meta: verify failed at file /dev/shm/foo offset 6291456, length 65536
> fio: pid=55393, err=84/file:io_u.c:1806, func=io_u_queued_complete,
> error=Invalid or incomplete multibyte or wide character
> go: (groupid=0, jobs=1): err=84 (file:io_u.c:1806,
> func=io_u_queued_complete, error=Invalid or incomplete multibyte or
> wide character): pid=55393: Tue Aug 5 15:56:56 2014
>
> Switching --loops=4 for --time_based --runtime=1m doesn't resulted in
> the same error.
>
> Is this fio job malformed?
No, the job is fine, it's yet another case where the numberio
verification for meta fails miserably. Try current git, I committed a
one liner for it.
--
Jens Axboe
next prev parent reply other threads:[~2014-08-07 21:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 15:22 Spurious verification mismatch? Sitsofe Wheeler
2014-08-07 21:27 ` Jens Axboe [this message]
2014-08-12 4:56 ` Sitsofe Wheeler
2014-08-13 20:15 ` Jens Axboe
2014-08-28 22:03 ` Sitsofe Wheeler
2014-08-28 22:57 ` Elliott, Robert (Server Storage)
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=53E3EF3E.8090204@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sitsofe@gmail.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