| Classes in this File | Line Coverage | Branch Coverage | Complexity | ||||
| ErrorType |
|
| 0.0;0 |
| 1 | package org.jscsi.target.scsi.sense; | |
| 2 | ||
| 3 | /** | |
| 4 | * Describes the type of error that makes it necessary to send of sense data to the initiator. | |
| 5 | * | |
| 6 | * @author Andreas Ergenzinger | |
| 7 | */ | |
| 8 | 0 | public enum ErrorType { |
| 9 | /** | |
| 10 | * Current errors (indicated by sense response codes 70h and 72h) indicate that the sense data returned is the | |
| 11 | * result of an error or exception condition on the task that returned the CHECK CONDITION status or a protocol | |
| 12 | * specific failure condition. This includes errors generated during processing of the command. It also includes | |
| 13 | * errors not related to any command that are detected during processing of a command (e.g., disk servo-mechanism | |
| 14 | * failure, off-track errors, or power-up test errors). | |
| 15 | */ | |
| 16 | 0 | CURRENT, |
| 17 | /** | |
| 18 | * Deferred errors (indicated by sense response codes 71h and 73h) indicate that the sense data returned is the | |
| 19 | * result of an error or exception condition that occurred during processing of a previous command for which GOOD, | |
| 20 | * CONDITION MET, INTERMEDIATE, and INTERMEDIATE-CONDITION MET status has already been returned. Such commands are | |
| 21 | * associated with the use of the immediate bit and with some forms of caching. Device servers that implement these | |
| 22 | * features shall implement deferred error reporting. | |
| 23 | */ | |
| 24 | 0 | DEFERRED |
| 25 | } |