User guide

exer
The exer command returns an error code immediately after a read, write, or
compare error, if the D_HARDERR environment variable is set to HALT. When
an error occurs and continue or loop on error is specified, then subsequent
operations specified by the action string option occur except for comparisons. For
instance, if a read error occurs, a subsequent comparison is skipped since a read
failure preceding a compare operation guarantees that the comparison fails. If
subsequent block I/O operations succeed, comparisons of those blocks occur.
When the exer command terminates because of completing all passes or by
operator termination, the status returned is that of the last failed write, read, or
compare operation, regardless of subsequent successful I/O operations.
Examples
1.
>>> exer dk*.* -p 0 -secs 36000
Read all SCSI type disks for the entire length of each disk. Repeat this until
36000 seconds (10 hours) have elapsed. All disks are read concurrently. Each
block read occurs at a random block number on each disk.
2.
>>> exer -l 2 dka0
Read block numbers 0 and 1 from device dka0 .
3.
>>> exer -sb 1 -eb 3 -bc 4 -a ’w’ -d1 ’0x5a’ dka0
Write 0x5as to every byte of blocks 1, 2, and 3. The packet size is bc * bs, 4 *
512, 2048 for all writes.
4.
>>> ls -l du*.* dk*.*
d**.* no such file
r--- dk 0/0 0 dka0.0.0.0.0
>>> exer dk*.* -bc 10 -sec 20 -m -a ’r’
dka0.0.0.0.0 exer completed
packet IOs elapsed idle
size IOs bytes read bytes written /sec bytes/sec seconds secs
8192 3325 27238400 0 166 1360288 20 19
Console Commands 13–45