From: Jens Axboe <axboe@kernel.dk>
To: Alket Memushaj <amemushaj@gmail.com>, fio@vger.kernel.org
Subject: Re: unable to replay a trace generated w/ fio
Date: Mon, 19 May 2014 13:47:09 -0600 [thread overview]
Message-ID: <537A5FBD.6010303@kernel.dk> (raw)
In-Reply-To: <CA+BkS8PN4EOofkBNc+NWO0kXYayE6c=dqmKYLfv96ZZanS=rBQ@mail.gmail.com>
On 2014-05-18 04:01, Alket Memushaj wrote:
> I am not having luck with 2.1.7 either, but anything up to 2.0.11
> works. It seems to terminate as soon as it completes reading the trace
> file - at the end of which I have /dev/sdb close as that's what's
> generated by fio itself when I set write_iolog=<file>
I'll take a look, I bet it's an issue from around the time the file
opening logic was added.
Can you send the exact job you used to create and replay files? Will
make my life easier.
--
Jens Axboe
next prev parent reply other threads:[~2014-05-19 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-17 11:52 unable to replay a trace generated w/ fio Alket Memushaj
2014-05-17 12:10 ` Alket Memushaj
2014-05-18 10:01 ` Alket Memushaj
2014-05-19 19:47 ` Jens Axboe [this message]
2014-06-05 19:02 ` Allen Schade
2014-06-05 20:21 ` Allen Schade
2014-06-10 1:53 ` Jens Axboe
2014-06-10 1:57 ` Jens Axboe
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=537A5FBD.6010303@kernel.dk \
--to=axboe@kernel.dk \
--cc=amemushaj@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox