Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

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

See Also
       Guide to System Exercisers

																	   dskx(8)

Check Out this Related Man Page

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

Name
       fsx - file system exerciser

Syntax
       /usr/field/fsx [ -h ] [ -ofile ] [ -tn ] [ -fpath ] [ -pm ]

Description
       The exerciser exercises a file system by spawning up to 250 (the default is 20) processes that create, open, write, close, open, read, val-
       idate, close, and unlink a test file.  These test files are created in (the default) unless the -fpath option is used. 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.

Options
       The options are:

       -h     Print the help messages for the command.

       -ofile Save the output diagnostics in file.

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

       -pm    Number (m) of processes to spawn.  The maximum is 250; the default is 20.

       -fpath Path name of directory on file system you wish to test.  For example, or The default is

Examples
       The following example runs 10 processes on until the process receives a or kill -15 pid:
       % /usr/field/fsx -p10 -f/mnt
       The following example runs 20 processes on for 120 minutes in the background:
       % /usr/field/fsx -t120 &

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.  Avoid using the  exerciser  over	an
       NFS or diskless file system.

See Also
       Guide to System Exercisers

																	    fsx(8)
Man Page