scsi标准指令集SBC4

scsi

5星 · 超过95%的资源需积分: 11 99 浏览量更新于2023-07-10 评论收藏 1.35MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源评论

资源推荐

Working Draft Project

American National T10/1799-D

Standard

Revision 22

29 March 2010

Information technology -

SCSI Block Commands – 3 (SBC-3)

This is an internal working document of T10, a Technical Committee of Accredited Standards Committee

INCITS (International Committee for Information Technology Standards). As such this is not a completed

standard and has not been approved. The contents may be modified by the T10 Technical Committee. The

contents are actively being modified by T10. This document is made available for review and comment only.

Permission is granted to members of INCITS, its technical committees, and their associated task groups to

reproduce this document for the purposes of INCITS standardization activities without further permission,

provided this notice is included. All other rights are reserved. Any duplication of this document for commercial

or for-profit use is strictly prohibited.

T10 Technical Editor: Mark Evans

Western Digital Corporation

5863 Rue Ferrari

San Jose, CA 95138

USA

Telephone: 408-363-5257

Email: mark.evans@wdc.com

Reference number

ISO/IEC 14776-323:200x

ANSI INCITS.***:200x

T10/1799-D Revision 22 29 March 2010

iv Working Draft SCSI Block Commands – 3 (SBC-3)

Published by

American National Standards Institute

11 W. 42nd Street, New York, New York 10036

No part of this publication may by reproduced in any

form, in an electronic retrieval system or otherwise,

without prior written permission of ITI, 1101 K Street, NW Suite 610,

Washington, DC 20005.

Printed in the United States of America

American

National

Standard

Approval of an American National Standard requires verification by ANSI that the

requirements for due process, consensus, and other criteria for approval have been met by

the standards developer. Consensus is established when, in the judgment of the ANSI Board

of Standards Review, substantial agreement has been reached by directly and materially

affected interests. Substantial agreement means much more than a simple majority, but not

necessarily unanimity. Consensus requires that all views and objections be considered, and

that effort be made towards their resolution.

The use of American National Standards is completely voluntary; their existence does not in

any respect preclude anyone, whether he has approved the standards or not, from

manufacturing, marketing, purchasing, or using products, processes, or procedures not

conforming to the standards.

The American National Standards Institute does not develop standards and will in no

circumstances give interpretation on any American National Standard. Moreover, no person

shall have the right or authority to issue an interpretation of an American National Standard

in the name of the American National Standards Institute. Requests for interpretations

should be addressed to the secretariat or sponsor whose name appears on the title page of

this standard.

CAUTION NOTICE: This American National Standard may be revised or withdrawn at any

time. The procedures of the American National Standards Institute require that action be

taken periodically to reaffirm, revise, or withdraw this standard. Purchasers of American

National Standards may receive current information on all standards by calling or writing the

American National Standards Institute.

CAUTION: The developers of this standard have requested that holders of patents that

may be required for the implementation of the standard, disclose such patents to the

publisher. However, neither the developers nor the publisher have undertaken a patent

search in order to identify which, if any, patents may apply to this standard. As of the date

of publication of this standard, following calls for the identification of patents that may be

required for the implementation of the standard, no such claims have been made. No

further patent search is conducted by the developer or the publisher in respect to any

standard it processes. No representation is made or implied that licenses are not

required to avoid infringement in the use of this standard.

29 March 2010 T10/1799-D Revision 22

Working Draft SCSI Block Commands – 3 (SBC-3) v

Revision History

R.1 Revision 0 (09 September 2005)

Revision 0 of SBC-3 is substantially equal to revision 16 of SBC-2. The only differences arise from changes

made in SBC-2 discovered during the ISO process. Those changes include:

a) Changed idle condition timer to standby condition timer in item c) of subclause 4.15.1.

b) Changed 2 Gigabytes to 1 GiB and 2 Terabytes to 2 TiB in two places in note 10 in subclause 5.5.

The 2 was change to a 1 because there are 21 bits in the

LOGICAL BLOCK ADDRESS field (i.e., 1F_FFFF

is 2 097 151 that * 512 is 1 073 741 312 which is 1 GiB).

Removed the

CORRCT bit from the WRITE LONG (16) CDB as it was never supposed to be added to this

command. It's not in SCSI-2 or SBC for WRITE LONG (10) and 03-383r1 did not ask for it. It showed up in

sbc2r11.

R.2 Revision 1 (16 September 2005)

a) Incorporated the following proposals:

A) 04-198r5 - Background Media Scan;

B) 04-371r2 - SPC-4: Enable Background Operation Error Reporting Bit; and

C) 05-101r1 - SBC-2 Validation of Protection Information.

R.3 Revision 2 (22 September 2005)

a) Incorporated the following proposals:

A) 05-299r1 - Correct Log Page Format Tables in SPC-4, SBC-3, & SAS-2; and

B) 05-313r0 - SBC-3: Change to background medium scan.

R.4 Revision 3 (16 November 2005)

a) Incorporated the following proposals:

A) 05-156r7 - SBC-3, SPC-4: Application ownership of protection information Reference Tag;

B) 05-317r3 - SMC-3, SPC-4, SBC-3, and SSC-3: Remove Attached Media Changer model; and

C) 05-374r2 - SBC-3: SPC-4: Disabling Reassign on Write Long Logical Blocks.

R.5 Revision 4 (10 February 2006)

a) Incorporated the following proposals:

A) 05-157r9 - SPC Security Commands proposal (in an E-mail it was pointed out that the

SERCURITY PROTOCOL IN and SECURITY PROTOCOL OUT commands need to be added to

the SBC-3 commands list table);

B) 05-340r3 - SBC-3 SPC-4 Background scan additions;

C) 05-368r2 - SPC-4 SBC-3 SMC-3 Allow more commands through Write Exclusive reservations;

and

D) 05-383r4 - SPC-4: Deferred microcode downloads.

In addition the following editorial corrections were received from E-mail were incorporated:

a) the initiator control (

IC) enable bit description had the SIZE bit polarity backwards;

b) changed filed to field;

c) WRITE SAME (32) was placed into the list of medium access commands in the Protection types

overview subclause;

d) the field name

P_TYPEABLE in table 19 (FMTPINFO bit, RTO_REQ bit, and PROTECTION FIELD USAGE field)

footnote d was changed to

P_TYPE; and

e) the field name

DATA BLOCK GUARD in table 80 (LBDATA bit and PBDATA bit) in row 0 0 was changed to

LOGICAL BLOCK GUARD.

R.6 Revision 5 (11 May 2006)

a) Incorporated the following proposals:

剩余255页未读，继续阅读

snowflack510

2015-09-01

非常完整的一份文档，找很久了，非常不错，谢谢共享。

PolarisChow

粉丝: 3
资源: 25

会员权益专享

scsi标准指令集SBC4

评论4

会员权益专享

最新资源

scsi标准指令集SBC4

评论4

论文研究-面向嵌入式系统的威胁建模与风险评估.pdf

SCSI Block Commands – 4 (SBC-4)

非常好的软件工程讲义 John C. Knight

scsi spc/sbc的指令集

scsi命令参考手册

node.js sbc解码

ffmpeg sbc转mp3

ffmpeg sbc转wav

sbc格式文件导出文字

wav2sbc.exe

用c语言写一个sbc转pcm的算法

sbc 编码格式在哪下载

mmc_request结构体sbc

ffmpeg sbc转pcm

施瓦茨贝叶斯准则 (SBC)

SBC stream

iphone怎么设置成sbc

sbc与cscf有什么关系

wav转sbc工具下载

wav2sbc.exe下载

会员权益专享

最新资源