SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001The AVAILABLE DATA field shall contain the number of bytes following the AVAILABLE DATA field in the parameter data(i.e., the total number of parameter data bytes minus 4).The MAXIMUM TARGET COUNT field contains the maximum number of target descriptors that the copy managerallows in a single EXTENDED COPY target descriptor list.The MAXIMUM SEGMENT COUNT field contains the maximum number of segment descriptors that the copy managerallows in a single EXTENDED COPY segment descriptor list.The MAXIMUM DESCRIPTOR LIST LENGTH field contains the maximum length, in bytes, of the target descriptor list andsegment descriptor list. This length includes the embedded data but excludes inline data that follows thedescriptors.The MAXIMUM SEGMENT LENGTH field indicates the length, in bytes, of the largest amount of data that the copymanager supports writing via a single segment. Bytes introduced as a result of the PAD bit being set to one (see7.2.7) are not counted towards this limit. A value of zero indicates that the copy manager places no limits on theamount of data written by a single segment.The MAXIMUM INLINE DATA LENGTH field indicates the length, in bytes, of the largest amount of inline data that thecopy manager supports in the EXTENDED COPY parameter list. This does not include data included asembedded data within the segment descriptors. The MAXIMUM INLINE DATA LENGTH field applies only to segmentdescriptors containing the 04h descriptor type code (see 7.2.7.7). The field shall be set to zero when the 04hdescriptor type code is not supported by the copy manager.The HELD DATA LIMIT field indicates the length, in bytes, of the minimum amount of data the copy managerguarantees to hold for return to the application client via the RECEIVE COPY RESULTS command with RECEIVEDATA service action (see 7.14.3). If the processing of segment descriptors requires more data to be held, the copymanager may discard some of the held data in a vendor specific manner that retains the held bytes from the mostrecently processed segment descriptors. The discarding of held data bytes shall not be considered an error. Ifheld data is discarded, the hdd bit shall be set as described in 7.14.2.The MAXIMUM CONCURRENT COPIES field contains the maximum number of EXTENDED COPY commandssupported for concurrent processing by the copy manager.The DATA SEGMENT GRANULARITY field indicates the length of the smallest data block that copy manager permits ina non-inline segment descriptor (i.e., segment descriptors with type codes other than 04h). The amount of datatransferred by a single segment descriptor shall be a multiple of the granularity. The DATA SEGMENT GRANULARITYvalue is expressed as a power of two. Bytes introduced as a result of the PAD bit being set to one (see 7.2.7) arenot counted towards the data length granularity.The INLINE DATA GRANULARITY field indicates the length of the of the smallest block of inline data that the copymanager permits being written by a segment descriptor containing the 04h descriptor type code (see 7.2.7.7). Theamount of inline data written by a single segment descriptor shall be a multiple of the granularity. The INLINE DATAGRANULARITY value is expressed as a power of two. Bytes introduced as a result of the PAD bit being set to one (see7.2.7) are not counted towards the length granularity.If the copy manager encounters a data or inline segment descriptor that violates either the data segment granularityor the inline data granularity, the EXTENDED COPY command shall be terminated with a CHECKCONDITION status. The sense key shall be set to COPY ABORTED and the additional sense code shall be set toCOPY SEGMENT GRANULARITY VIOLATION.The HELD DATA GRANULARITY field indicates the length of the smallest block of held data that the copy manager shalltransfer to the application client in response to a RECEIVE COPY RESULTS command with RECEIVE DATA124 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20service action (see 7.14.3). The amount of data held by the copy manager in response to any one segmentdescriptor shall be a multiple of this granularity. The HELD DATA GRANULARITY value is expressed as a power of two.The MAXIMUM STREAM DEVICE TRANSFER SIZE field indicates the maximum transfer size, in bytes, supported forstream devices.The IMPLEMENTED DESCRIPTOR LIST LENGTH field contains the length, in bytes, of the list of implemented descriptortype codes.The list of implemented descriptor type codes contains one byte for each segment or target DESCRIPTOR TYPE CODEvalue (see 7.2.5) supported by the copy manager, with a unique supported DESCRIPTOR TYPE CODE value in eachbyte. The DESCRIPTOR TYPE CODE values shall appear in the list in ascending numerical order.7.14.5 FAILED SEGMENT DETAILS service actionIn response to the FAILED SEGMENT DETAILS service action, the copy manager shall return details of thesegment processing failure that caused termination of the EXTENDED COPY command (see 7.2) identified by theLIST IDENTIFIER field in the CDB. Table 92 shows the format of the information returned by the copy manager inresponse to a FAILED SEGMENT DETAILS service action. If a device server supports the EXTENDED COPYcommand (see 7.4), then it shall also support the RECEIVE COPY RESULTS command with FAILED SEGMENTDETAILS service action.When processing of an EXTENDED COPY command is aborted and processing of a segment descriptor is incomplete,the copy manager shall preserve details about the progress in processing of that descriptor. These detailsenable the application client to obtain information it needs to determine the state in which target devices (inparticular stream devices) have been left by incomplete processing.If the LIST IDENTIFIER field of a RECEIVE COPY RESULTS CDB identifies an EXTENDED COPY command that stillis being processed by the copy manager, the command shall be terminated with a CHECK CONDITION status.The sense key shall be set to ILLEGAL REQUEST and the additional sense code shall be set to INVALID FIELD INCDB.Table 92 — Parameter data for the FAILED SEGMENT DETAILS service actionBitByte7 6 5 4 3 2 1 00 (MSB)AVAILABLE DATA (n-4)3 (LSB)4Reserved5556 EXTENDED COPY COMMAND STATUS57 Reserved58 (MSB)SENSE DATA LENGTH (n-59)59 (LSB)60SENSE DATAndpANS SCSI Primary Commands - 2 (SPC-2) 125
Page 1 and 2:
dpANSProjectT10/1236-DRevision 2018
Page 3:
DraftANSI (r)NCITS.351:200xAmerican
Page 6 and 7:
T10/1236-D Revision 20 18 July 2001
Page 8 and 9:
Page 10 and 11:
Page 12 and 13:
Page 14 and 15:
Page 16 and 17:
Page 18 and 19:
Page 20 and 21:
Page 22 and 23:
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93: T10/1236-D Revision 20 18 July 2001
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
show all

SCSI Primary Commands - 2.pdf

Create successful ePaper yourself

Delete template?

Save as template?