SCSI Primary Commands - 2.pdf

More documents

Recommendations

Info

T10/1236-D Revision 20 18 July 2001Reservations may be further qualified by restrictions on types of access (e.g., read, write, control). However, anyrestrictions based on the type of reservation are independent of the scope of the reservation. In addition, somemethods of reservation management permit establishing reservations on behalf of another device in the sameSCSI domain (third-party reservations).The methods of managing reservations are identified by the commands associated with the methods. Themethods of managing reservations are:a) Reserve/Release (see 5.5.2) - associated with the RESERVE(10), RELEASE(10), RESERVE(6), andRELEASE(6) commands (see 7.21, 7.16, 7.22, and 7.17, respectively); andb) Persistent Reservations (see 5.5.3) - associated with the PERSISTENT RESERVE OUT andPERSISTENT RESERVE IN commands (see 7.11 and 7.10, respectively).The two methods are prevented from creating conflicting and undefined interactions using RESERVATIONCONFLICT status in the following manner. If a logical unit has executed a PERSISTENT RESERVE OUTcommand with the REGISTER or the REGISTER AND IGNORE EXISTING KEY service action and is still registeredby any initiator, all RESERVE commands and all RELEASE commands regardless of initiator shall conflictand shall terminate with a RESERVATION CONFLICT status. If a logical unit has been reserved by any RESERVEcommand and is still reserved by any initiator, all PERSISTENT RESERVE IN and all PERSISTENT RESERVEOUT commands shall conflict regardless of initiator or service action and shall terminate with a RESERVATIONCONFLICT status.Reservation restrictions are placed on commands as a result of access qualifiers associated with the type of reservation.The details of which commands are allowed under what types of reservations are described in table 10.For the reservation restrictions placed on commands for the reserve/release management method see table 10column [A]. For the reservation restrictions placed on commands for the persistent reservations managementmethod see the table 10 columns under [B].If any element is reserved within a logical unit, that logical unit shall be considered reserved for the commandslisted in table 10 and the accept/conflict information in table 10 shall apply.In table 10 and table 11 the following key words are used:allowed: Commands issued by initiators not holding the reservation or by initiators not registered when a registrantsonly persistent reservation is present should complete normally.conflict: Commands issued by initiators not holding the reservation or by initiators not registered when a registrantsonly persistent reservation is present shall not be performed and the device server shall terminate thecommand with a RESERVATION CONFLICT status.Commands from initiators holding a reservation should complete normally. The behavior of commands from registeredinitiators when a registrants only persistent reservation is present is specified in table 10 and table 11.A command that does not explicitly write the medium shall be checked for reservation conflicts before thecommand enters the current task state for the first time. Once the command has entered the current task state, itshall not be terminated with a RESERVATION CONFLICT due to a subsequent reservation.A command that explicitly writes the medium shall be checked for reservation conflicts before the device servermodifies the medium or cache as a result of the command. Once the command has modified the medium, it shallnot be terminated with a RESERVATION CONFLICT due to a subsequent reservation.For each command, this standard or a related command standard (see 3.1.12) defines the conditions that result inRESERVATION CONFLICT. Command standards define the conditions either in the device model (preferred) or in24 dpANS SCSI Primary Commands - 2 (SPC-2)
18 July 2001 T10/1236-D Revision 20the descriptions each specific command. Annex B contains the RESERVATION CONFLICT information for someof the command sets.Table 10 — SPC commands that are allowed in the presence of various reservationsCommandAddressedLU isreservedby anotherinitiator[A]Addressed LU has this type of persistent reservationheld by another initiator[B]From any initiatorWriteExclExclAccessFromregisteredinitiator(RO alltypes)From initiator notregisteredWrite ExclROExcl Access– ROEXTENDED COPY Conflict Conflict Conflict Allowed Conflict ConflictINQUIRY Allowed Allowed Allowed Allowed Allowed AllowedLOG SELECT Conflict Conflict Conflict Allowed Conflict ConflictLOG SENSE Allowed Allowed Allowed Allowed Allowed AllowedMODE SELECT(6)/MODE SELECT(10)Conflict Conflict Conflict Allowed Conflict ConflictMODE SENSE(6)/MODE SENSE(10)Conflict Conflict Conflict Allowed Conflict ConflictPERSISTENT RESERVE IN Conflict Allowed Allowed Allowed Allowed AllowedPERSISTENT RESERVE OUT see table 11PREVENT/ALLOW (Prevent=0) Allowed Allowed Allowed Allowed Allowed AllowedPREVENT/ALLOW (Prevent0) Conflict Conflict Conflict Allowed Conflict ConflictREAD BUFFER Conflict Conflict Conflict Allowed Conflict ConflictRECEIVE COPY RESULTS Conflict Conflict Conflict Allowed Conflict ConflictRECEIVE DIAGNOSTICS Conflict Conflict Conflict Allowed Conflict ConflictRELEASE(6)/RELEASE(10) Allowed a Conflict Conflict Conflict Conflict ConflictREPORT DEVICE IDENTIFIER Allowed Allowed Allowed Allowed Allowed AllowedREPORT LUNS Allowed Allowed Allowed Allowed Allowed AllowedREQUEST SENSE Allowed Allowed Allowed Allowed Allowed AllowedRESERVE(6)/RESERVE(10) Conflict Conflict Conflict Conflict Conflict ConflictSEND DIAGNOSTICS Conflict Conflict Conflict Allowed Conflict ConflictSET DEVICE IDENTIFIER Conflict Conflict Conflict Allowed Conflict ConflictTEST UNIT READY Conflict Conflict Conflict Allowed Conflict ConflictWRITE BUFFER Conflict Conflict Conflict Allowed Conflict ConflictKey: LU=Logical Unit, Excl=Exclusive, RO=Registrants Only, Not Equala The reservation is not released (see 7.16 and 7.17).dpANS SCSI Primary Commands - 2 (SPC-2) 25
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 92 and 93:
T10/1236-D Revision 20 18 July 2001
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?