From: Sitsofe Wheeler <sitsofe@yahoo.com>
To: "Lamkin, Eric" <Eric.Lamkin@lsi.com>
Cc: David Nellans <david@nellans.org>,
"fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: fio replay
Date: Wed, 26 Feb 2014 15:30:20 +0000 [thread overview]
Message-ID: <20140226153017.GA31124@sucs.org> (raw)
In-Reply-To: <934f861a97f2443aa35296c2d6d8c848@BN1PR07MB437.namprd07.prod.outlook.com>
Hi,
I've been using blktrace with fio by doing the following on Fedora 20
with a git version of fio (fio-2.1.5-16-g81fa):
blktrace -d /dev/sdd
blkparse sdd -O -d sdd.dump
fio --read_iolog=sdd.dump --ioengine=libaio --name=replay
Using iowatcher I can see that fio is hitting the same blocks that the
blktrace recorded.
It is also worth noting that certain options like rate, rate_iops and bs
do not seem to affect replay jobs. Additionally, fio does not seem able
to replay a job with the same timings that it is was recorded with (it
also seems to do so faster) whereas btreplay has no issue doing this
(even reproducing similar depths to the original job).
The one minor issue that I see is this:
Run status group 0 (all jobs):
READ: io=40549MB, aggrb=30919KB/s, minb=30919KB/s, maxb=30919KB/s, mint=1342918msec, maxt=1342918msec
WRITE: io=40562MB, aggrb=30929KB/s, minb=30929KB/s, maxb=30929KB/s, mint=1342918msec, maxt=1342918msec
fio: file hash not empty on exit
Why is the file hash not empty on exit? This happens no matter what I
do.
On Wed, Feb 26, 2014 at 02:23:27PM +0000, Lamkin, Eric wrote:
>
> Thanks for responding.
> I sent the below out last week but didn't get a reply so thought I'd
> try a simpler 'what works' tactic this morning. As seen in the below
> I'm using 2.0.10.
>
> > On Feb 26, 2014, at 7:44 AM, "Lamkin, Eric" <Eric.Lamkin@lsi.com> wrote:
> >
> > Is there a version of fio where replay works with a Linux blktrace?
> >
> anything within the last few years should play them back just fine, is
> it broken in a specific version you're trying?
--
Sitsofe | http://sucs.org/~sits/
next prev parent reply other threads:[~2014-02-26 15:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 13:44 fio replay Lamkin, Eric
2014-02-26 14:13 ` David Nellans
2014-02-26 14:23 ` Lamkin, Eric
2014-02-26 15:30 ` Sitsofe Wheeler [this message]
2014-02-26 15:48 ` Lamkin, Eric
2014-02-26 16:15 ` Sitsofe Wheeler
2014-02-26 17:49 ` Jens Axboe
2014-02-26 21:44 ` Jens Axboe
2014-02-26 21:55 ` Lamkin, Eric
2014-02-27 18:48 ` Jens Axboe
2014-02-27 20:12 ` Lamkin, Eric
2014-03-03 13:25 ` Lamkin, Eric
2014-03-04 3:12 ` Alireza Haghdoost
2014-03-04 13:37 ` Lamkin, Eric
2014-03-06 15:55 ` Jens Axboe
2014-03-06 16:12 ` Lamkin, Eric
2014-03-28 13:52 ` Lamkin, Eric
2014-04-10 15:37 ` Lamkin, Eric
-- strict thread matches above, loose matches on Subject: below --
2014-02-20 16:39 Lamkin, Eric
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=20140226153017.GA31124@sucs.org \
--to=sitsofe@yahoo.com \
--cc=Eric.Lamkin@lsi.com \
--cc=david@nellans.org \
--cc=fio@vger.kernel.org \
/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.