dskx(8) [ultrix man page]

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

Name
dskx - generic disk exerciser

Syntax
/usr/field/dskx [ options ] -rdev
/usr/field/dskx [ options ] -pdevpart
/usr/field/dskx [ options ] -cdev

Description
The exerciser tests the disk drives on your system. The exerciser has three main options which include read only, write/read/validate data
on a partition, and write/read/validate data of a disk.

The exerciser does random seeks and reads of random block sizes and random seeks, writes, reads, and validations of random data patterns of
random block sizes. The exerciser will run until or kill -15 pid is sent to the process.

A logfile is made in for you to examine and then remove. If there are errors in the logfile, make sure you check the file, because that is
where the driver and kernel error messages are saved.

CAUTION: Both the -c and -p options of the exerciser destroy data on the disk. Use extreme caution before using them on any non-scratch
media. If you are unsure of what data is on the disk, contact your system manager before running with either of these options.

Arguments
One of the following function flags and arguments must be specified.

-rdev Performs a random read-only test on all partitions except the c partition. The dev argument can be a raw or buffered device name
and number. For example, rhp0, ra3, hk1.

-pdevpart Writes, reads, and validates data from the device name and number specified by dev and the partition specified by part. The dev
argument can be a raw or buffered device name and number. For example, rhp0, ra3, hk1. The part argument can be any valid par-
tition from a - h.

CAUTION: Be careful when exercising partitions that overlap other partitions, as you may inadvertently destroy data on a parti-
tion that you do not want to test. You can use the -q option of the command to see what partitions overlap on the device on your
system.

-cdev Writes, reads, and validates data from all partitions except the c partition on the device specified by dev. The dev argument
can be a raw or buffered device name and number. For example, rhp0, ra3, hk1.

Options
The options are:

-h Prints help message for the command.

-ofile Saves output diagnostics in file.

-tn Specifies the run time in minutes (n). The default is to run until the process receives a or kill -15 pid.

-dm Prints statistics every m minutes.

Restrictions
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as the target file system must be writable by root. Also the directory, in which any of the exer-
cisers are executed, must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.

Examples
The following example exercises RA disk unit 1, for 60 minutes in the background:
% /usr/field/dskx -t60 -cra1 &
The following example exercises raw HP disk unit 0, partition d, until or kill -15 pid:
% /usr/field/dskx -prhp0d

Check Out this Related Man Page

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

NAME

       cmx - Generic communication exerciser

SYNOPSIS

       /usr/field/cmx [-b [minbaud]-[maxbaud]] [-h] [-ofile] [-tn] -l line-n...

OPTIONS

       Use this option to specify the minimum, maximum, or range of baud rates to test.  Prints help messages about the cmx command.  Test all the
       listed tty lines, where n equals the lines to test according to the special device file entries in the /dev directory, such as 00,  12,	or
       42-53  Saves  output diagnostics in file.  Specifies the run time in minutes (n).  The default is to run until a [CTRL-C] or a kill -15 pid
       is sent to the process.

DESCRIPTION

       The cmx exerciser writes, reads, and validates random data and packet lengths on a specified communications line.  The  line  being  tested
       must  have a loopback connector attached to the distribution panel, or the cable and the line must be disabled in the /etc/inittab file and
       a non-modem line; the CLOCAL option must be set to on.

       The exerciser runs until a [CTRL-C] or a kill -15 pid is sent to the process.

       A logfile for you to examine and then remove is created in the current working directory; errors can be listed in the logfile.

       You must specify the -l option followed by the lines to test. The line-n arguments identify the lines to be tested. A maximum of  32  lines
       can  be	tested at any one time.  The line-n arguments are specified as names taken from the /dev directory without the letters "tty."  For
       example, if the /dev directory lists tty03, the line-n argument is 03.

       The Devices section lists the devices that can be tested.

RESTRICTIONS

       If you want to run a system exerciser over an NFS link or on a diskless system, there are some restrictions.  For exercisers such as fsx(8)
       that need to write into a file system, the target file system must be writable by root. Also, the directory from which an exerciser is exe-
       cuted must be writable by root because temporary files are written into the directory.  These restrictions can be difficult  to	adhere	to
       because	NFS file systems are often mounted in a way that prevents root from writing into them.	Some of the restrictions may be adhered to
       by copying the exerciser into another directory and then executing it.

       Pseudo devices (devices whose first character after tty is any alphabetic character, other than lowercase d) cannot be  tested.	 Also  lat
       devices with major #5 cannot be tested.

DEVICES

       Use the file command on /dev/tty* to find out which tty line corresponds to a device line number.

EXAMPLES

       The following example runs the cmx exerciser for 60 minutes on lines 00, 13, 22, and 32: % /usr/field/cmx -t60 -l 00 13 22 32 The following
       example runs the cmx exerciser on lines 11, 42, 45, and 76 in the background until  interrupted	by  a  [CTRL-C]  or  a	kill  -15  pid:  %
       /usr/field/cmx  -l  11  42  45  76  & The following example runs the cmx exerciser on line 11, specifying a range of baud rates to test.  %
       /usr/field/cmx -b9600-38400 -l 11

SEE ALSO

       Commands: diskx(8), fsx(8), memx(8), shmx(8), tapex(8)

																	    cmx(8)

Linux and UNIX Man Pages

dskx(8) [ultrix man page]

Check Out this Related Man Page