From: Jens Axboe <jaxboe@fusionio.com>
To: Hsiao Su <Hsiao.Su@marklogic.com>
Cc: "fio@vger.kernel.org" <fio@vger.kernel.org>
Subject: Re: using blktrace, blkparse, and fio
Date: Mon, 28 Feb 2011 08:06:52 -0500 [thread overview]
Message-ID: <4D6B9DEC.2080805@fusionio.com> (raw)
In-Reply-To: <E9E9B636B25C054B8E6B9131614B925A039046CC@EXCHG-BE.marklogic.com>
On 2011-02-25 13:24, Hsiao Su wrote:
>
> Thanks,
>
> A follow up question. Suppose that I use fio directly, without
> blktrace and blkparse. In this case, I would have to guess the real
> IO workload that my app is doing, and specify that in the job file.
> Would I still have to worry about file system corruption?
>
> My guess is no for this one, that fio would create its own file for
> replaying the workload.
Depends on what the job looks like. If you stick to writing to files in
a mounted fs, it'll work fine. If you tell fio to use
--filename=/dev/sda or whatever the device is, you'll corrupt the file
system(s) if that job file is doing writes.
--
Jens Axboe
next prev parent reply other threads:[~2011-02-28 13:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-24 19:13 using blktrace, blkparse, and fio Hsiao Su
2011-02-25 7:58 ` Jens Axboe
2011-02-25 18:24 ` Hsiao Su
2011-02-28 13:06 ` Jens Axboe [this message]
2011-02-28 20:16 ` Hsiao Su
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=4D6B9DEC.2080805@fusionio.com \
--to=jaxboe@fusionio.com \
--cc=Hsiao.Su@marklogic.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.