From: Jens Axboe <jens.axboe@oracle.com>
To: "Sebastian Färber" <faerber@gmail.com>
Cc: fio@vger.kernel.org
Subject: Re: replay blktrace to different device
Date: Mon, 17 May 2010 19:42:34 +0200 [thread overview]
Message-ID: <20100517174233.GQ25951@kernel.dk> (raw)
In-Reply-To: <AANLkTilwHeA9olwqW5PFcvotNxuCqfoN5_iyUe6PokFh@mail.gmail.com>
On Sun, May 16 2010, Sebastian F�rber wrote:
> > I'm running fio like this:
> > # fio --name=replay --filename=/dev/sdc --read_iolog=trace_input_fio
> > and it aborts with
> > fio: filesetup.c:855: get_file: Assertion `fio_file_open(f)' failed.
>
> I captured another trace, this time for /dev/sdc, tried again using it
> as input to read_iolog
> and got the same error message.
> So it looks like there is a general problem with "read_iolog" in fio 1.38?
> I can supply the "--debug=all" logfile if needed.
I'll take a look.
--
Jens Axboe
next prev parent reply other threads:[~2010-05-17 17:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-16 14:54 replay blktrace to different device Sebastian Färber
2010-05-16 15:50 ` Sebastian Färber
2010-05-17 17:42 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-11-20 7:34 Alireza Haghdoost
2010-11-21 12:37 ` 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=20100517174233.GQ25951@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=faerber@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 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.