From: Jens Axboe <axboe@kernel.dk>
To: Sitsofe Wheeler <sitsofe@gmail.com>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: Should io_limits/queue depth flushed persist while using verify_state?
Date: Thu, 15 Jan 2015 15:45:54 -0700 [thread overview]
Message-ID: <54B84322.10704@kernel.dk> (raw)
In-Reply-To: <CALjAwxgmpWDviJiUyoXSZPy_-JP0va+QdXmhP-r6g6JTTRv7Fg@mail.gmail.com>
On 01/15/2015 04:01 AM, Sitsofe Wheeler wrote:
> While using fio-2.2.4 the following snippet produces a verification
> error for me on the second fio invocation:
>
> fio --bs=4k --ioengine=libaio --direct=1 --verify=meta --iodepth=128
> --io_limit=300k --verify_state_save=1 --rw=randwrite --name=write3
> --filename=/dev/dm-7 && fio --bs=4k --ioengine=libaio --direct=1
> --verify=meta --iodepth=128 --verify_state_load=1 --rw=randread
> --name=write3 --filename=/dev/dm-7
>
> However if I put the iodepth of the second fio command down to 64 or
> set io_limit the error goes away. I have also sometimes seen an error
> that looks similar if the first fio is killed via ctrl-C. Is this to
> be expected?
Doesn't reproduce here, but both cases would seem to imply that there's
something not quite right with the completed ios in the verify state
output. I'll take a look.
--
Jens Axboe
next prev parent reply other threads:[~2015-01-15 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 11:01 Should io_limits/queue depth flushed persist while using verify_state? Sitsofe Wheeler
2015-01-15 22:45 ` Jens Axboe [this message]
2015-01-16 17:24 ` Jens Axboe
2015-01-17 9:11 ` Sitsofe Wheeler
2015-01-29 6:18 ` Sitsofe Wheeler
2015-01-29 16:43 ` Jens Axboe
2015-02-15 13:07 ` Sitsofe Wheeler
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=54B84322.10704@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 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.