.TH SG_TEST_RWBUF "8" "January 2018" "sg3_utils\-1.43" SG3_UTILS
sg_test_rwbuf \- test a SCSI host adapter by issuing dummy writes
[\fI\-\-addrd=AR\fR] [\fI\-\-addwr=AW\fR] [\fI\-\-help\fR]
[\fI\-\-quick\fR] \fI\-\-size=SZ\fR [\fI\-\-times=NUM\fR] [\fI\-\-verbose\fR]
or an older deprecated format
\fIDEVICE\fR \fISZ\fR [\fIAW\fR] [\fIAR\fR]
.\" Add any additional description here
sg_test_rwbuf writes and reads back \fISZ\fR bytes to the internal buffer of
\fIDEVICE\fR (e.g. /dev/sda or /dev/sg0). A pseudo random pattern is
written to the data buffer on the device then read back. If the same pattern
is found 'Success' is reported. If they do not match (checksums unequal) then
this is reported and up to 24 bytes from the first point of mismatch are
reported; the first line shows what was written and the second line shows
what was received. For testing purposes, you can ask it to write \fIAW\fR or
read \fIAR\fR additional bytes.
Arguments to long options are mandatory for short options as well.
Read an additional \fIAR\fR bytes (more than indicated by \fISZ\fR) from the
data buffer. Checksum is performed over the first \fISZ\fR bytes.
Write an additional \fIAW\fR bytes (more than indicated by \fISZ\fR) of
zeros into the data buffer. Checksum is generated over the first \fISZ\fR
Print out a usage message the exit.
Perform a READ BUFFER descriptor command to find out the available data
buffer length and offset, print them out then exit (without testing
with write/read sequences).
where \fISZ\fR is the size of buffer in bytes to be written then read and
checked. This number needs to be less than or equal to the size of the
device's data buffer which can be seen from the \fI\-\-quick\fR option.
Either this option or the \fI\-\-quick\fR option should be given.
where \fINUM\fR is the number of times to repeat the write/read to buffer
test. Default value is 1 .
increase verbosity of output.
print version number (and data of last change) then exit.
The microcode in a SCSI device is _not_ modified by doing a WRITE BUFFER
command with its mode set to "data" (0x2) as done by this utility. Therefore
this utility is safe in that respect. [Mode values 0x4, 0x5, 0x6 and 0x7
are the dangerous ones :\-)]
\fBWARNING\fR: If you access the device at the same time (e.g. because it's
a hard disk with a mounted file system on it) the device's buffer may be
used by the device itself for other data at the same time, and overwriting
it may or may not cause data corruption! \fBHOWEVER\fR the SPC\-3 draft
standard does state in its WRITE BUFFER command: "This command shall not
alter any medium of the logical unit when data mode ... is specified". This
implies that it _is_ safe to use this utility with devices that have mounted
file systems on them.
Following this theme further, a disk with active mounted file systems may
cause the data read back to be different (due to caching activity) to what
was written and hence a checksum error.
.SH EXIT STATUS
The exit status of sg_test_rwbuf is 0 when it is successful. Otherwise see
the sg3_utils(8) man page.
Written by D. Gilbert and K. Garloff
Copyright \(co 2000\-2018 Douglas Gilbert, Kurt Garloff
This software is distributed under the GPL version 2. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.