SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001While performing a self-test in the background mode, the device server shall suspend the self-test to service anyother commands received with the exceptions listed in table 8. Suspension of the self-test to service the commandshall occur as soon as practical and shall not take longer than two seconds.Table 8 — Exception commands for background self-testsDevice type Command ReferenceAll device typesSEND DIAGNOSTICS (with SELF-TEST CODE field set to 100b)WRITE BUFFER (with the mode set to any download microcode option)Direct access FORMAT UNIT START/STOP UNIT SBCSequentialaccessMediumchangerNOTE 1ERASEFORMAT MEDIUMLOAD UNLOADLOCATEREADREAD POSITIONREAD REVERSEREWINDSPACEVERIFYWRITEWRITE BUFFERWRITE FILEMARKSEXCHANGE MEDIUMINITIALIZE ELEMENT STATUSMOVE MEDIUMPOSITION TO ELEMENTREAD ELEMENT STATUS (if CURDATA=0 and device motion is required)WRITE BUFFERIf one of the exception commands listed in table 8 is received, the device server shall abort the self-test, update theself-test log, and service the command as soon as practical but not longer than two seconds after the CDB hasbeen validated.An application client may terminate a self-test that is being performed in the background mode by issuing a SENDDIAGNOSTICS command with the SELF-TEST CODE field set to 100b (Abort background self-test function).5.4.3.3 Elements common to foreground and background self-test modesThe PROGRESS INDICATION field returned in response to a REQUEST SENSE command (see 7.20) may be used bythe application client at any time during a self-test operation to poll the logical unit’s progress. While a self-testoperation is in progress unless an error has occurred, a device server shall respond to a REQUEST SENSEcommand by returning a sense key of NOT READY and an additional sense code of LOGICAL UNIT NOT READY,SELF-TEST IN PROGRESS with the sense key specific bytes set for progress indication.The application client may obtain information about the twenty most recently completed self-tests by reading theself-test results log page (see 8.2.8). This is the only method for an application client to obtain information aboutself-tests performed in the background mode.7.237.26SSCSMCDevice types not listed in this table do not have commands that are exceptions for backgroundself-tests, other than those listed above for all device types.22 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20Table 9 summarizes when a logical unit returns status after receipt of a self-test command, how an applicationclient may abort a self-test, how a logical unit handles new commands that are received while a self-test is inprogress, and how a logical unit reports a self-test failure.Table 9 — Self-test mode summaryModeWhenStatus isReturnedHow to abortthe self-testProcessing of subsequentcommands while self-test isexecutingSelf-test failure reportingForegroundAfter theself-test iscompleteABORT TASKtask managementfunctionIf the command is INQUIRY,REPORT LUNS or REQUESTSENSE, process normally.Otherwise, terminate withCHECK CONDITION status,NOT READY sense key, andLOGICAL UNIT NOT READY,SELF-TEST IN PROGRESSadditional sense code.Terminate with CHECK CONDI-TION status, HARDWAREERROR sense key, and LOGICALUNIT FAILED SELF-TESTor LOGICAL UNIT UNABLE TOUPDATE SELF-TEST LOG additionalsense code.BackgroundAfter theCDB isvalidatedSEND DIAG-NOSTICScommand withSELF-TEST CODEfield set to 100bProcess the command,except as described in5.4.3.2.Application client checks Self-testresults log page (see 8.2.8) afterthe PROGRESS INDICATION fieldreturned from REQUEST SENSEindicates the self-test is complete5.5 Reservations5.5.1 Reservations overviewReservations may be used to allow a device server to execute commands from a selected set of initiators. Thedevice server shall reject commands from initiators outside the selected set of initiators by uniquely identifying initiatorsusing protocol specific mechanisms.Application clients may add or remove initiators from the selected set using reservation commands. If the applicationclients do not cooperate in the reservation protocol, data may be unexpectedly modified and deadlock conditionsmay occur.The general description of reservations involves two groups of considerations;a) the type of reservation established, andb) the method used to establish, rescind, and manage the reservation.There are limits on the combinations of reservation types available under some reservation management methods.See the reservations management commands descriptions for details.The scope of a reservation shall be one of the following:a) logical unit reservations - a logical unit reservation restricts access to the entire logical unit; andb) element reservations - an element reservation restricts access to a specified element within a mediumchanger.dpANS SCSI Primary Commands - 2 (SPC-2) 23
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 90 and 91:
T10/1236-D Revision 20 18 July 2001
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 142 and 143:
Page 144 and 145:
Page 146 and 147:
Page 148 and 149:
Page 150 and 151:
Page 152 and 153:
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?