From: Jens Axboe <axboe@kernel.dk>
To: Lakshmi Devi <sendtold@gmail.com>, fio@vger.kernel.org
Subject: Re: Blktrace replay in FIO failed with lseek err=22
Date: Tue, 19 Nov 2013 14:28:29 -0700 [thread overview]
Message-ID: <528BD7FD.4060706@kernel.dk> (raw)
In-Reply-To: <CAEyTGCcDDgN=5Oa0J_40Q2F=uoGSZkAtrbR0npzjZLzfmSZ=EQ@mail.gmail.com>
On 11/19/2013 10:12 AM, Lakshmi Devi wrote:
> Hi,
>
> I am using FIO version 2.1.1 and blktrace 2.0.0
>
> I ran a read, 4K workload through FIO and collected blktrace for it.
> I got like 16 trace files one for each CPU core with varying sizes.
>
> I parsed one of the files as below
> blkparse -i ./*.blktrace.0 -d ./bp.bin -o bp.txt -w 0:600
>
> used this bp.bin to perform a read_iolog in FIO.
>
> When I replay in FIO using read_iolog=/root/bp.bin , I get the below error.
>
> Replay: (groupid=0, jobs=1): err=22 file engine sync.c: 45, func=lseek,
> error=invalid argument.
>
> Please help me understand the reason for this error
Would it be possible for you to send me the bp.bin output file?
--
Jens Axboe
prev parent reply other threads:[~2013-11-19 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 17:12 Blktrace replay in FIO failed with lseek err=22 Lakshmi Devi
2013-11-19 21:28 ` Jens Axboe [this message]
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=528BD7FD.4060706@kernel.dk \
--to=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=sendtold@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.