Some targets send a spurious CHECK CONDITION message in response to the first SCSI command. We issue (and ignore the status of) an arbitary harmless SCSI command (a READ CAPACITY (10)) in order to draw out this response. The Solaris Comstar target seems to send more than one spurious CHECK CONDITION response. Attempt up to SCSI_MAX_DUMMY_READ_CAP dummy READ CAPACITY (10) commands before assuming that error responses are meaningful. Problem reported by Kristof Van Doorsselaere <kvandoor@aserver.com> and Shiva Shankar <802.11e@gmail.com>.tags/v0.9.7
|
|
||
29 |
|
29 |
|
30 |
|
30 |
|
31 |
|
31 |
|
|
32 |
|
|
|
33 |
|
|
|
34 |
|
|
|
35 |
|
|
|
36 |
|
|
|
37 |
|
|
|
38 |
|
|
32 |
|
39 |
|
33 |
|
40 |
|
34 |
|
41 |
|
|
|
||
250 |
|
257 |
|
251 |
|
258 |
|
252 |
|
259 |
|
|
260 |
|
|
253 |
|
261 |
|
254 |
|
262 |
|
255 |
|
|
|
256 |
|
|
|
257 |
|
|
|
258 |
|
|
|
|
263 |
|
|
|
264 |
|
|
|
265 |
|
|
|
266 |
|
|
|
267 |
|
|
|
268 |
|
|
|
269 |
|
|
259 |
|
270 |
|
260 |
|
|
|
|
271 |
|
|
|
272 |
|
|
|
273 |
|
|
|
274 |
|
|
261 |
|
275 |
|
262 |
|
276 |
|
263 |
|
277 |
|