blob: 118dc1050285d88f8ac3394f0602649022afc176 [file] [log] [blame]
.TH BTREPLAY 8 "December 8, 2007" "blktrace git\-20071207142532" ""
btreplay \- recreate IO loads recorded by blktrace
.B btreplay [ \fIoptions\fR ] <\fIdev\fR...>
The \fIbtrecord\fR and \fIbtreplay\fR tools provide the ability to
record and replay IOs captured by the \fIblktrace\fR utility. Attempts
are made to maintain ordering, CPU mappings and time-separation of IOs.
The \fIblktrace\fR utility provides the ability to collect detailed
traces from the kernel for each IO processed by the block IO layer. The
traces provide a complete timeline for each IO processed, including
detailed information concerning when an IO was first received by the block
IO layer \(em indicating the device, CPU number, time stamp, IO direction,
sector number and IO size (number of sectors). Using this information,
one is able to \fBreplay\fR the IO again on the same machine or another
set up entirely.
The basic operating work-flow to replay IOs would be something like:
.IP \- 2
Run \fIblktrace\fR to collect traces. Here you specify the
device or devices that you wish to trace and later replay IOs upon. Note:
the only traces you are interested in are \fBQUEUE\fR requests \(em
thus, to save system resources (including storage for traces), one could
specify the \fI-a queue\fR command line option to \fIblktrace\fR.
.IP \- 2
While \fIblktrace\fR is running, you run the workload that you
are interested in.
.IP \- 2
When the work load has completed, you stop the \fIblktrace\fR
utility (thus saving all traces over the complete workload).
.IP \- 2
You extract the pertinent IO information from the traces saved by
\fIblktrace\fR using the \fIbtrecord\fR utility. This will parse
each trace file created by \fIblktrace\fR, and crafty IO descriptions
to be used in the next phase of the workload processing.
.IP \- 2
Once \fIbtrecord\fR has successfully created a series of data
files to be processed, you can run the \fIbtreplay\fR utility which
attempts to generate the same IOs seen during the sample workload phase.
\-c <\fInum\fR>
Set number of CPUs to use.
\-d <\fIdir\fR>
Set input directory.
This option requires a single parameter providing the directory
name for where input files are to be found. The default directory is the
current directory (\fI.\fR).
Find record files automatically
This option instructs \fIbtreplay\fR to go find all the record files in the
directory specified (either via the \fI-d\fR option, or in the default
directory (\fI.\fR).
Show help and exit.
\-i <\fIbasename\fR>
Set base name for input files.
Each input file has 3 fields:
.IP 1. 3
Device identifier (taken directly from the device name of the
\fIblktrace\fR output file).
.IP 2. 3
\fIbtrecord\fR base name \(em by default ``replay''.
.IP 3. 3
The CPU number (again, taken directly from the
\fIblktrace\fR output file name).
This option requires a single parameter that will override the default name
(replay), and replace it with the specified value.
\-I <\fInum\fR>
Set number of iterations to run.
This option requires a single parameter which specifies the number of times
to run through the input files. The default value is 1
\-M <\fIfilename\fR>
Specify device mappings.
This option requires a single parameter which specifies the name of a
file contain device mappings. The file must be very simply managed, with
just two pieces of data per line:
.IP \- 2
The device name on the recorded system (with the '\fI/dev/\fR'
removed). Example: \fI/dev/sda\fR would just be \fIsda\fR.
.IP \- 2
The device name on the replay system to use (again, without the
'\fI/dev/\fR' path prepended).
An example file for when one would map devices \fI/dev/sda\fR and
\fI/dev/sdb\fR on the recorded system to \fIdev/sdg\fR and
\fIsdh\fR on the replay system would be:
sda sdg
sdb sdh
The only entries in the file that are allowed are these two element lines \(em
we do not (yet?) support the notion of blank lines, or comment lines, or the
The utility allows for multiple \fI-M\fR options to be
supplied on the command line.
Disable pre-bunch stalls.
When specified on the command line, all pre-bunch stall indicators will be
ignored. IOs will be replayed without inter-bunch delays.
\-x <\fIfactor\fR>
Specify acceleration factor. Default value is 1 (no acceleration).
Enable verbose output.
When specified on the command line, this option instructs \fIbtreplay\fR
to store information concerning each \fBstall\fR and IO operation
performed by \fIbtreplay\fR. The name of each file so created will be
the input file name used with an extension of \fI.rep\fR appended onto
it. Thus, an input file of the name \fIsdab.replay.3\fR would generate a
verbose output file with the name \fIsdab.replay.3.rep\fR in the
directory specified for input files.
In addition, \fIbtreplay\fR will also output to \fIstderr\fR the
names of the input files being processed.
Show version number and exit.
Enable writing during replay.
As a precautionary measure, by default \fIbtreplay\fR will not
process \fBwrite\fR requests. In order to enable \fIbtreplay\fR to
actually \fBwrite\fR to devices one must explicitly specify the
\fI\-W\fR option.
\fIbtreplay\fR was written by Alan D. Brunelle. This
man page was created from the \fIbtreplay\fR documentation by Bas Zoetekouw.
Report bugs to <linux\>
Copyright \(co 2007 Alan D. Brunelle, Alan D. Brunelle and Nathan Scott.
This is free software. You may redistribute copies of it under the terms of
the GNU General Public License <>.
There is NO WARRANTY, to the extent permitted by law.
This manual page was created for Debian by Bas Zoetekouw. It was derived from
the documentation provided by the authors and it may be used, distributed and
modified under the terms of the GNU General Public License, version 2.
On Debian systems, the text of the GNU General Public License can be found in
The full documentation for btreplay can be found in /usr/share/doc/blktrace on Debian systems.
blktrace (8), blkparse (1), btrecord (8)