From 429e750032737616a8a80222257d510db77753e0 Mon Sep 17 00:00:00 2001 From: Douglas Gilbert Date: Sun, 30 Sep 2012 19:55:15 +0000 Subject: sg_verify: manpage git-svn-id: https://svn.bingwo.ca/repos/sg3_utils/trunk@460 6180dd3e-e324-4e3e-922d-17de1ae2f315 --- doc/sg_verify.8 | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) (limited to 'doc/sg_verify.8') diff --git a/doc/sg_verify.8 b/doc/sg_verify.8 index 90f1e332..4947eb50 100644 --- a/doc/sg_verify.8 +++ b/doc/sg_verify.8 @@ -1,4 +1,4 @@ -.TH SG_VERIFY "8" "February 2012" "sg3_utils\-1.33" SG3_UTILS +.TH SG_VERIFY "8" "September 2012" "sg3_utils\-1.34" SG3_UTILS .SH NAME sg_verify \- invoke SCSI VERIFY command(s) on a block device .SH SYNOPSIS @@ -43,7 +43,9 @@ this option is ignored if \fI\-\-bytchk=NDO\fR is given. Otherwise \fIBPC\fR specifies the maximum number of blocks that will be verified by a single SCSI VERIFY command. The default value is 128 blocks which equates to 64 KB for a disk with 512 byte blocks. If \fIBPC\fR is less than \fICOUNT\fR then -multiple SCSI VERIFY commands are sent to the device. For recent block +multiple SCSI VERIFY commands are sent to the device. For the default +VERIFY(10) \fIBPC\fR cannot exceed 0xffff (65,535) while for VERIFY(16) +\fIBPC\fR cannot exceed 0x7fffffff (2,147,483,647). For recent block devices (disks) this value may be constrained by the maximum transfer length field in the block limits VPD page. .TP -- cgit v1.2.3