disktest/man1/disktest_manual.html

Content-type: text/html

<HTML><HEAD><TITLE>Manpage of DISKTEST</TITLE>
</HEAD><BODY>
<H1>DISKTEST</H1>
Section: Diag Tools (1)<BR>Updated: March 2007<BR><A HREF="#index">Index</A>
<A HREF="http://localhost/cgi-bin/man/man2html">Return to Main Contents</A><HR>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>

disktest - Test tool for exersizing disk devices
<A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2>

<B>disktest [-q] [-Q] [-r] [-w] [-E</B>

<I>cmp_length</I>

<B>] [-a</B>

<I>seed</I>

<B>] [ -A</B>

<I>action</I>

<B>] [-z|c|n|f</B>

<I>fixed_pattern</I>

<B>] [-B</B>

<I>sBLK[:eBLK]</I>

<B>| -C</B>

<I>cycles</I>

<B>] [-d ] [-D</B>

<I>r%:w%</I>

<B>] [-F] [-h</B>

<I>heartbeat</I>

<B>] [-K</B>

<I>threads</I>

<B>| -L</B>

<I>seeks</I>

<B>] [-P</B>

<I>TXPRCA</I>

<B>] [ -m ] [-N</B>

<I>sectors</I>

<B>] [-R</B>

<I>retry[:retryDelay]</I>

<B>] [-o</B>

<I>offset</I>

<B>] [-s</B>

<I>sLBA[:eLBA]</I>

<B>] [-S</B>

<I>sBLK[:eBLK]</I>

<B>] [-t</B>

<I>delayMin[[:[delayMax]][:ioTimeout]]</I>

<B>] [-T</B>

<I>seconds</I>

<B>] [-p</B>

r
<B>|</B>

R
<B>|</B>

l
<B>[</B>

u
<B>|</B>

d
<B>]</B>

<B>] |</B>

L
<B>[</B>

u
<B>|</B>

d
<B>]] [-I [</B>

d
<B>]</B>

r
<B>|</B>

b
<B>|</B>

f
<B>[</B>

s [ delay ]
<B>]</B>

<B>]</B>

<I>filespec</I>

<A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2>

<B>Disktest</B>

does repeated accesses to a
<I>filespec</I>

and optionally writes to, reads from, and verifies the data.  By default,
<B>disktest</B>

makes assumptions about the running environment which allows for a quick start of IO generation.  However,
<B>Disktest</B>

has a large number of command line options which can be used to adapt the test for a variety of uses including data integrity, medium integrity, performance, and simple application simulation.
<P>
<B>Disktest</B>

will use the device specified by
<I>filespec.</I>

If no option is specified otherwise,
<B>disktest</B>

will attempt to determine
<I>filespec</I>

type.  Fully qualified path must be give when
<I>filespec</I>

is not a normal file.  This will help to determine it's type.
<A NAME="lbAE">&nbsp;</A>
<H2>OPTIONS</H2>

Most options have multipliers that can be used to specify larger amounts.  The following are a list of these multipliers.
<DL COMPACT><DT><DD>
<P>
k = 1024, K = 10^3, m = 1024^2, M = 10^6, g = 1024^3, G = 10^9
<P>
</DL>

These can be used on options such as -B, -L, -N, -S, -s.  The time options also have multipliers.
<DL COMPACT><DT><DD>
<P>
m = 60, h = 60*60, d = 60*60*24
<P>
</DL>

These can be used on options such as -h and -T.
<DL COMPACT>
<DT>-?<DD>
Displays a short description of the command line options and exits normally.
<DT>-a seed<DD>
Use seed for all random number generation when constructing blocks of pseudo-random data and random seeks.
By default, seed is set to the process id number.
To reproduce a previous test run, use the process id number outputted to stdout.
<DT>-A action<DD>
These options are used to modify the default behavor during IO runtime.
The following options can be used for these modifications.
<DL COMPACT><DT><DD>
<DL COMPACT><DT><DD>
<DL COMPACT>
<DT>g<DD>
all threads, even to multiple targets, will be killed and the disktest process will stop.
By default, when an access failure occurs only the threads to the failing target will stop.
<DT>c<DD>
after error, all threads for all targets will continue to run.
<DT>r<DD>
the reread that would normally occur on a data miscompare is not performed.
<DT>m<DD>
after error, a special IO is sent to LBA 0 of the target.
This is so that a trigger can be set on the special data.
At the beginning if the IO is the string &quot;DISKTEST ERROR OCCURRED&quot;.
This will overwrite any mark data or normal pattern data written.
<DT>s<DD>
disable block level synchronization.
By default distest will synchronize IO on a block level according to the POSIX standard that states that an application must serialize IO to a block or raw device.
Disktest will not allow a write if the block is already being written or read, but will allow a read if other reads are occuring.
This option will turn off this checking.
<DT>S<DD>
enable IO serialization.
This addes to the synchronization of the threads, so that there is no more then one IO oustanding to a target, no matter how many threads are running to the target.
<DT>t<DD>
causes an IO timeout, to fail an IO run.
normally an IO timeout, see -t option, will just display a warning.
<DT>w<DD>
If running the -pR seek type, and this action is specified, then blocks will only be written once, and be read many times, i.e. WORM still testing.
This option does nothing with other seek pattern types, or if not reading and writing.
<P>
</DL>
</DL>

<B>NOTE:</B>

Options g and c are exclusive.
Option m cannot be specified with with c.
Option m cannot be specified if only reading from a device.
When using option s, it is possible that in some operating systems, that a data miscompare may result due to a kernel that does not garentee exclusion or does not handle well multiple readers and writers to the same block.
</DL>

<DT>-B sBlockSize[:eBlockSize]<DD>
Set the size of the data block transfer.  If only
<I>sBlockSize</I>

is specified, then the transfer length is always a fixed length of
<I>sBlockSize.</I>

If
<I>eBlockSize</I>

is specified, then the transfer length will be randomly chosen between
<I>sBlockSize</I>

and
<I>eBlockSize.</I>

The transfer size will always be a multipile of the sector size.
If either parameter is greater then 256, then the value will be integer divided by the sector size default, which is 512 bytes. If either parameter is preceded by a 'k', i.e. 8k, then the value will be multiplied by 1024. Otherwise, the parameters will be taken literally.  The default block size is (1*sector size) or 512.  Note that
<B>O_DIRECT</B>

, no filesystem buffering, and some file system may not be able to perform accesses as small as 512 bytes.  This will result in an IO failure with a transfer length of -1.
<DT>-c<DD>
Use a counting sequence for the bytes within to each block.  The count starts at 0 and increments to 255 then begins again at 0.  Each sector is filled with two of these sequences.
<DT>-C cycles<DD>
Run until the total number of
<I>cycles</I>

are complete.  When cycles is set to zero, disktest will run until killed.  The -L or -T option is used to specify how long each cycle will run for.  If neither -T or -L is specified, the cycle length with be calculated to the number of seeks based on the device size, -N, divided by the transfer size, -B. If -C is not specified, only a single cycle is run.
<DT>-d<DD>
Force
<B>disktest</B>

to dump to stdout the amount of data at the location specified by the other command-line option, i.e. -d -s50 -B 32k will dump 32768 bytes of data to stdout starting at LBA 50. The data is formatted into lines of 16 bytes with the location offset and ASCII equivalent.
<DT>-D r%:w%<DD>
Duty cycle used while reading and/or writing.  For example, -D 20:80 would cause
<B>disktest</B>

to generate a read 20% of the total run time and generate a write 80%.  If only read or write is give then the percentage is always set to 100 for the specified option.  If the total percentage does not add up to 100, i.e. -D 20:70, then
<B>disktest</B>

will split the remaining percentage, resulting in 25% reads and 75% writes.
<DT>-E compare_length<DD>
Turn on error checking.  Data read from
<I>filespec</I>

will be checked for correctness up to the number of bytes specified by
<I>compare_length.</I>

If
<I>compare_length</I>

is 0 then the block size is used as the compare length. By default, data read is not checked for errors.
<DT>-f fixed_pattern<DD>
Use a data pattern consisting of a fixed value.
<I>fixed_pattern</I>

can be entered using decimal, any number not starting with a 0, octel, any number staring with a 0, or hexadecimal, any number and [A-F] starting with 0x. The value can be no greater +/- 2^63, in size.
<DT>-F<DD>
used to specify that the
<I>filespec</I>

is actually a file listing the targets that
<B>disktest</B>

should operate on.  This allows
<B>disktest</B>

to run to multiple targets using the same options from a single command-line.
<DT>-h heartbeat<DD>
Performance data will be sent to stdout every
<I>heartbeat</I>

seconds. During a linear test, -pL, only heartbeat statistics for the current operational cycle will be displayed. The default is to only display performance data at the end of the test, which is cumulative for all IO performed throughout the test.
<DT>-I IO_type<DD>
Set the data transfer type to IO_type. Valid IO types are
<B>r</B>

(raw),
<B>b</B>

(block), or
<B>f</B>

(file) I/O.  These options are case sensitive.
<P>
The
<B>r</B>

(raw) type is used when binding a block device to a raw device, see
<B><A HREF="http://localhost/cgi-bin/man/man2html?8+raw">raw</A>(8). Disktest</B>

will align it's buffers correctly to support raw devices.
<P>
The
<B>b</B>

(block) type is used when block IO is desired.  The buffer_cache will be used during testing.  Buffer alignment is not required for this type of IO operation.
<P>
The
<B>f</B>

(file) type is used when accessing a file.  If the file does not exist then it will be created.  If the file exists, then it will opened; see
<B>O_CREAT</B>

in
<B><A HREF="http://localhost/cgi-bin/man/man2html?2+open">open</A>(2)</B>

for more details. Access to the file is performed through the file system that the file is stored on. Adding an S modifier to the F (file) type opertaions will force an
<B><A HREF="http://localhost/cgi-bin/man/man2html?2+fsync">fsync</A>(2)</B>

to occur on every write.
<P>
Adding
<B>d</B>

will open with the
<B>O_DIRECT</B>

flag set.
If this option is used, then I/O is limited to being aligned to the file systems block size.
When transferring to a block device w/o a file system, then alignment is to 1k.
These limits have been verified with the 2.4.9 kernel and the o_direct patch from AA.
<P>
Adding
<B>s</B>

<I>sync_interval</I>

Specifies that a sync should occur at
<I>sync_interval</I>

number of write IO operations. The default is to sync on every IO.
<P>
<B>Disktest</B>

will report a failure if
<I>filespec</I>

does not match the
<I>IO_type</I>

specified.
If no type is specified, then disktest will attempt to determine the file type by using <A HREF="http://localhost/cgi-bin/man/man2html?2+stat">stat</A>(2).
<DT>-K threads<DD>
Set the number of test threads to threads.  Each child can read or write based on the specified criteria.  The default number of test threads is 4.
<DT>-L seeks<DD>
Total number of seeks to occur during testing.  This option specifies the exact number of times a seek occurs on a resource.  By default
<B>disktest</B>

will calculate the number of seeks by taking the difference between the start block and the stop block.  If the difference is 0 then the default is 1000 seeks.
<DT>-m<DD>
This option will add the lba, pass count, seed, cycle start time, hostname, and target to each LBA as header data before any IO operation occurs. The mark replaces the first n bytes of data in each LBA.
<DT>-M marker<DD>
This option will override the cycle start time in the -m option with the specified value. This is useful when you are writing in one distest instance and read/verifing in another so that the mark data can be unique and also deterministic.
<DT>-n<DD>
Use a data pattern that consists of the the lba number.  An lba value of up to a 64b can be stored.  The 64b value is repeated to fill the transfer buffer.
<DT>-N sectors<DD>
Set the number of available sectors to num_secs. If no num_secs is specified, and the size of the device can be determined, then the number of sectors, as reported by the device is used, otherwise, the default number of sectors is 2000.
<DT>-o offset<DD>
This option specifies the LBA
<I>offset</I>

to shift all alignment of IO by.
For example, if a test is to perform a full stride write on a storage device, and the os and/or storage device offset the strides by a number of LBAs, this parameter can be used to set that offset, so that IO is aligned to the stride on the storage device.
By default the offset is set to zero.
<DT>-p seek_pattern<DD>
Set the pattern of seeks to
<I>seek_pattern.</I>

Valid patterns are
<B>l</B>

(linear interleaved writes/reads),
<B>L</B>

(linear writes then reads),
<B>R</B>

(random),
<B>r</B>

(random interleaved writes/reads).  Linear may also specify what happens when the last block is reached.  Option
<B>u</B>

specifies that the test should start back at first block after reaching the last block.
<B>d</B>

specifies that the test, after reaching the last block, should start at the last block and go to the first block. The default extra option for linear is 'u'. The default seek is random.
<DT>-P perf_opts<DD>
Record performance statistic to stdout. Perf_opts is a string of characters representing which statistics should be reported.  The possible options are:
<P>
<DL COMPACT><DT><DD>
<DL COMPACT><DT><DD>
<B>T</B>

- Disk throughput
<P>
<B>X</B>

- Number of transfers
<P>
<B>P</B>

- Display performance data in ';' delimited format
<P>
<B>R</B>

- Display runtime
<P>
<B>C</B>

- Display cycle performance details
<P>
<B>A</B>

- Display all performance options
<P>
</DL>

</DL>

<DT>-q<DD>
Suppress all the 'INFO' level messages that are send to stdout.  This includes all the assumption messages the
<B>disktest</B>

will print as it finds that the option was not specified in the command line arguments.
<DT>-Q<DD>
Suppress header data from messages that are send to stdout.
<DT>-r<DD>
Read from
<I>filespec.</I>

This is the default option if -w or -r are not specified.  -E must be specified if data integrity checking is desired.
<DT>-R retry[:retryDelay]<DD>
Specifies that on a seek or transfer error, the IO should be retried.
<I>retry</I>

Specifies the number of retry attempts that should be made.
<I>retryDelay</I>

Specifies the amount of time delay (msec) before the retry occurs.  If no
<I>retryDelay</I>

is specified, then retries will occur immediately.  By default, IO errors are not retried.
<DT>-S start_block[:end_block]<DD>
Set the starting test block to
<I>start_block</I>

and the ending test block to
<I>end_block.</I>

By default,
<I>start_block</I>

is 0 and
<I>end_block</I>

is 2000.  If
<I>end_block</I>

is not given, and the size of
<I>filespec</I>

can be determined, then
<I>end_block</I>

is set to the volume capacity reported by the device divided by the transfer length.
This option can only be used when there is a fixed transfer length.
The range given is inclusive, so if -S0:10 is specificed, this will be 11 blocks.
The -S and -s options are exclusive.
<DT>-s start_LBA[:end_LBA]<DD>
Set the starting test LBA to
<I>start_LBA</I>

and the ending test LBA to
<I>end_LBA.</I>

By default,
<I>start_LBA</I>

is 0 and
<I>end_LBA</I>

is 2000.  If
<I>end_LBA</I>

is not given, and the size of
<I>filespec</I>

can be determined, then
<I>end_LBA</I>

is set to the volume capacity reported by the device.
This option can only be used when there is a fixed transfer length.
The range given is inclusive, so if -s0:10 is specificed, this will be 11 LBAs.
The -S and -s options are exclusive.
<DT>-t delayMin[[:delayMax][:ioTimeout]]<DD>
Wait
<I>delayMin</I>

milliseconds between each IO.
This is used when attempting to simulate a static load from an application that has some known proccessing time between IO operations.
<I>delayMax</I>

can be added to specify that a per thread random IO delay should be used, between delayMin and delayMax.
When combined with multiple threads, -K, these can be used to model IO load for simulating application processing after IO.
By default, disktest will issue as many IO requests as possible, delayMin/delayMax is set to zero, which may over drive some disk subsystems when multiple hosts running disktest are attached to the same disk subsystem.
<P>
If no IOs complete in
<I>ioTimeout</I>

seconds, then disktest will consider the test to fail.
The default is now 60 secs, which means that if there are no IO operations to a target from any thread that complete in 60 secs then the test will stop with a failed status, and an ERROR message stating the there is a possible hung IO condition, if it is a true hung IO condition, then disktest IO threads will not terminate with a non-preemtable kernel, and the only error message with be from the ioTimeout ERROR message.
To disable this feature, set the io timeout to 0, which means that the IO timeout time will never be reached which is how disktest operated before this feature was added.
The minute, m, hour, h, and day, d, multipliers can also be used on these perameter.
The following are examples of -t usage.
<P>
<DL COMPACT><DT><DD>
<DL COMPACT><DT><DD>
-t0:0, is the default behavior as in previous versions
<P>
-t0:2h, is no IO delay, with a 2 hour IO timeout.
<P>
-t30, is a 30 msec delay, with default IO timeout.
<P>
-t300:1000:1m, is a random delay between 300:1000 msec, with a 1 minute io timeout.
<P>
</DL>

</DL>

<DT>-T runtime<DD>
Run until
<I>runtime</I>

seconds have elapsed.
<I>Runtime</I>

must always be greater than zero.  -T and -L are exclusive of one another.
<DT>-v<DD>
The version information will be displayed and
<B>disktest</B>

will exit normally.
<DT>-w<DD>
Write to
<I>filespec.</I>

Data will be written as fast as possible and not read back to check for data corruption. can be combined with -r option to do read/write testing and -E to perform data integrity checking.
<DT>-z<DD>
Use a randomly generated data pattern based on the seed for the bytes within to each block.  The data pattern is random for the first 512 bytes, one LBA.  The pattern is then repeated for each LBA after creating a pseudo random data pattern across the given
<I>filespec.</I>

This is done for two reasons.  One, it saves on the memory foot print size need and time required to generate the data, and two, an LBA is the smallest unit of work
<B>disktest</B>

operates on.  Therefore,
<B>disktest</B>

can maintain the ability to do data checking, random block size transfers, and random block offsets when using random data.
</DL>
<A NAME="lbAF">&nbsp;</A>
<H2>FILES</H2>

<I>./disktest</I>

<A NAME="lbAG">&nbsp;</A>
<H2>ENVIRONMENT</H2>

None.
<A NAME="lbAH">&nbsp;</A>
<H2>EXAMPLES</H2>

The following are some examples on how to use the options in
<B>disktest</B>

to create different types of workloads.  Please use these as a guideline to get started.
<P>
<DL COMPACT><DT><DD>
disktest -r -S10:15 -pld -L35 -B 256k -K3 -PTX /dev/sdaa
<P>
This will start a read test to blocks 10 through 15.  Seeks are linear and will be performed starting at 10 going to 15 then back to 10.  35 seeks will be performed.  The block size 256k and there will be three threads.  Also, total transfer and throughput will be displayed at the end of the test.
<P>
disktest -r -w -D30:70 -K2 -E32 -B 8192 -T 600 -pR -Ibd /dev/sdzz
<P>
This will start a write and read test were the work load is 30% reads and 70% writes.  There will be two threads and all read data will be checked for errors up to 32 bytes.  The block size is 8k and the test will run for 600 seconds.  Seeks will be random and /dev/sdzz will be opened with the
<B>O_DIRECT</B>

flag set.
<P>
disktest -K8 -t500:15000:120s ./testfile
<P>
This will start eight read threads, with a minimum read delay of 500 miliseconds, and a maximum of 15 seconds.
<P>
disktest -w -Is200 -R3:60000 -Ac -PRTX -B128k -T10 -pr ./afile
<P>
This will start four write threads, syncing every 200 IOs. If there is a error on any write, then the same IO will be retried up to 3 times, and the thread will wait for 60 seconds before attempting each retry. If there is an error during the test, just continue on, reporting all errors as warnings.
<P>
disktest -Ag -Am -B 16k -C 100 -K 1 -z -ma -pL -P A -S 0:20000 -r -w -E 0 -N 640032 ./afile
<P>
Start a read/write test with error checking for 100 cycles.  If there is an error, then write out the special marker to LBA 0 of the target, and stop all testing.  You random data, and all header markers.
<P>
</DL>
<A NAME="lbAI">&nbsp;</A>
<H2>DIAGNOSTICS</H2>

Output Format
<DL COMPACT><DT><DD>
All output has a header sting that displays in the following format:
<P>
<DL COMPACT><DT><DD>
| &lt;date&gt;-&lt;time&gt; | &lt;level&gt; | &lt;pid&gt; | &lt;version&gt; | &lt;device&gt; | &lt;message&gt;
<P>
</DL>

The first value is the system date and time.  It is expressed as:
<DL COMPACT><DT><DD>
&lt;MONTH&gt;/&lt;DAY&gt;/&lt;YEAR&gt;-&lt;HOUR&gt;:&lt;MIN&gt;:&lt;SEC&gt;.
<P>
</DL>

The second value is the level of the message.  Current levels include START, END, DEBUG, INFO, WARN, STAT, and ERROR.  The third value is the process id.  This can be used to match up the test processes with the output information if more then one test process is outputting to the same context, such as file. It can also be used to regenerate a test with the same seeks and random data using the -a. The fourth value is the revision number of the test process. The fifth is the target device.  The sixth is the informational message.  The following are some examples:
<DL COMPACT><DT><DD>
<P>
| 11/12/01-02:05:01 | START | 1314 | v1.2.3 | /dev/sdaa | Start args: -S100:105 -K5 -pid -r -PTX -L 25 -B 1 -z /dev/sdaa
<P>
| 11/12/01-02:05:01 | STAT  | 1314 | v1.2.3 | /dev/sdaa | 12800 bytes read in 25 transfers.
<P>
| 11/12/01-02:05:01 | STAT  | 1314 | v1.2.3 | /dev/sdaa | Read Throughput 12800B/s, IOPS 25/s.
<P>
| 11/12/01-02:05:01 | END   | 1314 | v1.2.3 | /dev/sdaa | Test Done (Passed)
<P>
</DL>

</DL>

Error Checking
<DL COMPACT><DT><DD>
When error checking is enabled, each read is compared with data that is generated by the command line options specified or assumptions made where no command line option is given.  If a data miscompare results the expected and actual data from the first 16 bytes of the LBA where the error occured is printed to STDOUT, and the IO thread will die without completing any other IO operations, unless the -A option is specified. if the compare_length is not zero, then only the first compare_length bytes are compared, and only if those bytes miscompare will a data miscompare be reported. When using the mark option, data miscompares can be more readly detect.
<P>
</DL>

Decoding Mark Data
<DL COMPACT><DT><DD>
When using the -m option, it will replace the first 32+ bytes of each LBA with mark information.
The + is the fact that it places the complete target information in the mark, so it can consume more or lease of the LBA depending on the filespec.
The mark information looks as follows:
<P>
<DL COMPACT><DT><DD>
00 00 00 00 00 00 00 D4 00 00 00 00 00 00 00 03
<BR>

00 00 00 00 42 FD 08 FD 00 00 00 00 00 00 43 FA
<BR>

69 6F 61 72 6B 00 00 00 00 00 00 00 00 00 00 00
<BR>

2E 2F 74 65 73 74 66 69 6C 65 3A 3B 3C 3D 3E 3F
<P>
</DL>

The first 8 bytes is the LBA, in this case
<DL COMPACT><DT><DD>
00 00 00 00 00 00 00 D4 : Which equals LBA #212
<P>
</DL>

The second 8 bytes is the pass count, in this case
<DL COMPACT><DT><DD>
00 00 00 00 00 00 00 03 : Which equals pass count 3
<P>
</DL>

The third 8 bytes is the start time, in this case
<DL COMPACT><DT><DD>
00 00 00 00 42 FD 08 FD : Which equals 0x42FD08FD or 1123879165 or Fri Aug 12 13:39:25 PDT 2005.
<BR>

This value is decoding using date --date=&quot;1970-01-01 1123879165 sec UTC&quot; .
<P>
</DL>

The fourth 8 bytes is the random seed, in this case
<DL COMPACT><DT><DD>
00 00 00 00 00 00 43 FA : Which equals 0x43FA
<P>
</DL>

The next 16 bytes is the first 16 bytes of the name of the host, in this case
<DL COMPACT><DT><DD>
69 6F 61 72 6B 00 00 00 00 00 00 00 00 00 00 00 : Which equals: ioark
<P>
</DL>

From the 49 byte on is the filespec, in this case
<DL COMPACT><DT><DD>
2E 2F 74 65 73 74  66 69 6C 65 : Which equals: ./testfile
</DL>

<P>
</DL>

Seeking/Accessing
<DL COMPACT><DT><DD>
When a seek failure occurs, the following information is sent to STDOUT:
<P>
<DL COMPACT><DT><DD>
| 11/12/01-02:05:01 | ERROR | 2250 | v1.2.3 | /dev/sdzz | lseek failed seek 10, lba = 32714, request pos = 1284, seek pos = -1, errno = 5
<P>
</DL>

When an access failure occurs, the following information is sent to STDOUT:
<P>
<DL COMPACT><DT><DD>
| 11/12/01-02:05:01 | ERROR | 4492 | v1.2.3 | /dev/sdxp | disk access failed: seek 10, lba = 32714, got = 0, asked for = 8192, errno = 2
<P>
</DL>

An access failure can also occur on a partial access.  In this case, 'got' will equal the number of bytes that were transfered.
Currently, distest treats partial accesses as failures, as distest attempts to always make sure that the LBA target and trasnfer size fits inside the specified volume size.
<P>
</DL>

Performance
<DL COMPACT><DT><DD>
Performance options will display information about throughput, IO per second, and runtime. This information can be print at the end of the test only, or throughout the test at a given interval using the heartbeat option, -h.
<P>
</DL>

Dumping
<DL COMPACT><DT><DD>
When dumping data from filespec you will specify -d along with other command-line options.  Here is an example:
<P>
<DL COMPACT><DT><DD>
disktest -d -B 1k -s25 /dev/sddz
<P>
</DL>

This will dump 1024 bytes of data to stdout starting at LBA 25.
<P>
</DL>

File I/O
<DL COMPACT><DT><DD>
Distest can be used to perform filesystem IO testing.  There is some setup required for this however.  Disktest will not automatically create a file on the filesystem.  Therefore, a file must be initialized.  This is only required for read only testing.  Write and read/write testing will create the file if not already created.  Also note, that when creating a file using random I/O, all the LBAs in the file may not be written.  This can cause disktest to show an error if a request is made to a file to an LBA that has not been previously written.  The follwing is an example to initialize a file for filesystem IO testing.
<P>
disktest -w -pl -N200000 -B128k test.fil
<P>
This will create a ~97MB file named test.fil in the current directory writing at 131072B per transfer.  Once this completes any type of IO test can be performed to this file. This can also be done by creating a sparce file by doing the following:
<P>
disktest -w -pl -K1 -L1 -S200000 test.fil
<P>
</DL>

<A NAME="lbAJ">&nbsp;</A>
<H2>TODO</H2>

The following are options that are forthcoming, ideas, and other good stuff:
<DL COMPACT><DT><DD>
Add the following options:
<DL COMPACT><DT><DD>
butterfly: seek option: test will seek lba start/end/start+1/end-1/etc...
<P>
non-destructive: will read lba/write lba with read data/then read lba to verify
<P>
min seek: force a minimum seek distance during any IO access
<P>
max seek: force a maximum seek distance during any IO access
<P>
WORO: all blocks will be written and read only once
<P>
WRWR: a block will be written then read then written then read
<P>
retry: number of times an I/O should be retried, after an error, before counting as a failure
<P>
</DL>
</DL>
<A NAME="lbAK">&nbsp;</A>
<H2>AUTHOR</H2>

Brent Yardley (<A HREF="mailto:yardleyb (a] us.ibm.com">yardleyb (a] us.ibm.com</A>)
<P>

<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">OPTIONS</A><DD>
<DT><A HREF="#lbAF">FILES</A><DD>
<DT><A HREF="#lbAG">ENVIRONMENT</A><DD>
<DT><A HREF="#lbAH">EXAMPLES</A><DD>
<DT><A HREF="#lbAI">DIAGNOSTICS</A><DD>
<DT><A HREF="#lbAJ">TODO</A><DD>
<DT><A HREF="#lbAK">AUTHOR</A><DD>
</DL>
<HR>
This document was created by
<A HREF="http://localhost/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 22:44:31 GMT, February 06, 2008
</BODY>
</HTML>