Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

drtest(8) [bsd man page]

DRTEST(8)						      System Manager's Manual							 DRTEST(8)

drtest - standalone disk test program DESCRIPTION
Drtest is a standalone program used to read a disk track by track. It was primarily intended as a test program for new standalone drivers, but has shown useful in other contexts as well, such as verifying disks and running speed tests. For example, when a disk has been format- ted (by format(8)), you can check that hard errors has been taken care of by running drtest. No hard errors should be found, but in many cases quite a few soft ECC errors will be reported. While drtest is running, the cylinder number is printed on the console for every 10th cylinder read. EXAMPLE
A sample run of drtest is shown below. In this example (using a 750), drtest is loaded from the root file system; usually it will be loaded from the machine's console storage device. Boldface means user input. As usual, ``#'' and ``@'' may be used to edit input. >>>B/3 %% loading hk(0,0)boot Boot : hk(0,0)drtest Test program for stand-alone up and hp driver Debugging level (1=bse, 2=ecc, 3=bse+ecc)? Enter disk name [type(adapter,unit), e.g. hp(1,3)]? hp(0,0) Device data: #cylinders=1024, #tracks=16, #sectors=32 Testing hp(0,0), chunk size is 16384 bytes. (chunk size is the number of bytes read per disk access) Start ...Make sure hp(0,0) is online ... (errors are reported as they occur) ... (...program restarts to allow checking other disks) ( abort halt machine with ^P) DIAGNOSTICS
The diagnostics are intended to be self explanatory. Note, however, that the device number in the diagnostic messages is identified as typeX instead of type(a,u) where X = a*8+u, e.g., hp(1,3) becomes hp11. SEE ALSO
format(8V), bad144(8) AUTHOR
Helge Skrivervik 4.2 Berkeley Distribution May 19, 1986 DRTEST(8)

Check Out this Related Man Page

zcav(8) 						      System Manager's Manual							   zcav(8)

zcav - program to test raw hard drive throughput. SYNOPSIS
zcav [-b block-size[:chunk-size]] [-c count] [-r [first-block]:last-block] [-w] [-s skip-rate] [-u uid-to-use:gid-to-use] [-g gid-to-use] [-l log-file] [-f] file-name [-l log-file [-f] file-name]... DESCRIPTION
This manual page documents briefly the zcav, program. Modern hard drives have a constant rotational speed but have varying numbers of sectors per track (outside tracks are longer and have more sectors). This is referred to as Zoned Constant Angular Velocity (or ZCAV). The outer tracks will have a higher data transfer rate due to having more sectors per track, these tracks generally have the lower track/sector numbers. This program tests the ZCAV performance of a hard drive, by reading the entire data on it a specified number of times. The file name given as the first parameter, it can be specified as -, for standard input. This file will be opened as read-only and in usual operation it will be /dev/hdX or /dev/ide/host0/busX/targetY/lun0/disc depending on whether you use devfs or not (NB operating systems other than Linux will have different device names). The output should be able to be easily graphed with gnuplot which is what I use to view the results. OPTIONS
-b the size (in Meg) of the blocks to read/write (default 100M), optionally followed by a ':' and the chunk size for read/write opera- tions (default 1M). Note that the chunk size must be less than or equal to the block size and must also be significantly less than the size of the RAM in the machine. Also note that for the write test there will be a fsync() after writing every chunk. -c the number of times to read/write the entire disk. -r the range of data (in Meg) to read/write on each pass (default the entire device). Useful if you want to quickly test part of a large drive. If a single number is given then that is the last block to read, if two numbers then it's the start and end of a range. Values are in megs, but they are rounded down to the block size. -s skip rate. The option -s 10 will cause it to read every 10th block and skip the rest. -f the file-name for the input data. This isn't needed on well configured systems that have a recent Glibc where you can specify the file name without the -f flag. -u user-id to use. When running as root specify the UID to run the tests as, it is not recommended to use root, so if you want to run as root use -u root. Also if you want to specify the group to run as then use the user:group format. If you specify a user by name but no group then the primary group of that user will be chosen. If you specify a user by number and no group then the group will be nogroup. -g group-id to use. Same as using :group for the -u parameter, just a different way to specify it for compatibility with other pro- grams. -w write zero blocks to the disk instead of reading from the disk - will destroy data! AUTHOR
This program, it's manual page, and the Debian package were written by Russell Coker <>. AVAILABILITY
The source is available from . See for further information. zcav(8)
Man Page