diff options
| author | Douglas Gilbert <dgilbert@interlog.com> | 2012-12-22 03:05:14 +0000 |
|---|---|---|
| committer | Douglas Gilbert <dgilbert@interlog.com> | 2012-12-22 03:05:14 +0000 |
| commit | 5915919120e2e85685d565c4537238889d2d9ab7 (patch) | |
| tree | 9c7c621837b1d1f63db6a02798ab7d4877d5b923 /doc/sg_write_same.8 | |
| parent | 07c24897e9c0345b43fca8e982ba22e5f9b8ea90 (diff) | |
| download | sg3_utils-5915919120e2e85685d565c4537238889d2d9ab7.tar.gz | |
another rescan-scsi-bus.sh patch; man page hyphens
git-svn-id: https://svn.bingwo.ca/repos/sg3_utils/trunk@472 6180dd3e-e324-4e3e-922d-17de1ae2f315
Diffstat (limited to 'doc/sg_write_same.8')
| -rw-r--r-- | doc/sg_write_same.8 | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/sg_write_same.8 b/doc/sg_write_same.8 index 146fb476..2d77e5a3 100644 --- a/doc/sg_write_same.8 +++ b/doc/sg_write_same.8 @@ -1,4 +1,4 @@ -.TH SG_WRITE_SAME "8" "November 2012" "sg3_utils\-1.35" SG3_UTILS +.TH SG_WRITE_SAME "8" "December 2012" "sg3_utils\-1.35" SG3_UTILS .SH NAME sg_write_same \- send SCSI WRITE SAME command .SH SYNOPSIS @@ -239,7 +239,7 @@ going to modify LBA 2468 then we take a copy of it first: The following command line sets the user data to zeroes and the PI to 8 0xFF bytes on LBA 2468: .PP - sg_write_same --lba=2468 /dev/sdb + sg_write_same \-\-lba=2468 /dev/sdb .PP Reading back that block should be successful because the application tag is 0xffff which suppresses the guard (CRC) check (which would otherwise be @@ -260,10 +260,10 @@ below shows: .br dd if=/dev/zero bs=1 count=2 seek=514 conv=notrunc of=lb.bin .PP -The resulting file can be viewed with 'hexdump -C lb.bin' and should +The resulting file can be viewed with 'hexdump \-C lb.bin' and should contain 520 bytes. Now that file can be written to LBA 2468 as follows: .PP - sg_write_same --lba=2468 wrprotect=3 --in=lb.bin /dev/sdb + sg_write_same \-\-lba=2468 wrprotect=3 \-\-in=lb.bin /dev/sdb .PP Note the \fI\-\-wrprotect=3\fR rather than being set to 1, since we want the WRITE SAME command to succeed even though the PI data now indicates @@ -274,7 +274,7 @@ error should occur: .PP dd errors are not very expressive, if dmesg is checked there should be a line something like this: "[sdb] Add. Sense: Logical block guard check -failed". The block can be corrected by doing a "sg_write_same --lba=1234 +failed". The block can be corrected by doing a "sg_write_same \-\-lba=1234 /dev/sdb" again or restoring the original contents of that LBA: .PP dd if=2468.bin bs=512 seek=2468 of=/dev/sdb conv=notrunc count=1 |