Package | Description |
---|---|
org.jscsi.target.scsi |
This package and its sub-packages contain all classes which represent SCSI byte structures, elements consisting of
one or more fields, which are used by SCSI devices to exchange information.
|
org.jscsi.target.scsi.inquiry |
This package contains all classes that are most pertinent to processing
INQUIRY SCSI commands. |
org.jscsi.target.scsi.lun |
The classes in this package represent SCSI elements that play a role in the processing of the
REPORT LUNS SCSI command. |
org.jscsi.target.scsi.modeSense |
This package contains all those classes which are most relevant to processing the
MODE SENSE (6) SCSI
command, which is used by the SCSI initiator to gather information about target devices. |
org.jscsi.target.scsi.readCapacity |
This package contains all those classes which are most relevant to processing any capacity requests.
|
org.jscsi.target.scsi.sense |
This package contains all classes which represent SCSI sense data - data which gives a detailed account of current or
deferred SCSI errors.
|
org.jscsi.target.scsi.sense.information |
This package contains classes representing the content of sense data
INFORMATION fields. |
org.jscsi.target.scsi.sense.senseDataDescriptor |
This package contains all classes that represent sense data descriptors, elements of sense data used to provide more
specific error information.
|
org.jscsi.target.scsi.sense.senseDataDescriptor.senseKeySpecific |
This package contains all classes representing sense-key specific data, which is a part of sense-key specific sense
data descriptors.
|
Modifier and Type | Interface and Description |
---|---|
interface |
IResponseData
In addition to dictating the serialization methods inherited from
ISerializable , this interface serves as a
marker interface for all classes that can be sent as SCSI Response data, i.e. |
Modifier and Type | Class and Description |
---|---|
class |
DeviceIdentificationVpdPage
The Device Identification VPD page provides the means to retrieve identification descriptors applying to the logical
unit.
|
class |
IdentificationDescriptor
Instances of this class contain information identifying the logical unit, SCSI target device containing the logical
unit, or access path (i.e., target port) used by the command and returned parameter data.
|
class |
Identifier
The IDENTIFIER field is part of an IDENTIFICATION DESCRIPTOR and, as its name implies, contains identifying
information about the references entity.
|
class |
ScsiNameStringIdentifier
The null-terminated, null-padded (see 4.4.2) SCSI NAME STRING field contains a UTF-8 format string.
|
class |
StandardInquiryData
The standard inquiry data, sent as a response to an
ScsiOperationCode.INQUIRY command. |
class |
SupportedVpdPages
This Vital Product Data page contains a list of the VPD page codes supported by the logical unit.
|
Modifier and Type | Class and Description |
---|---|
class |
LogicalUnitNumber
A 64-bit identifier for a logical unit.
|
class |
ReportLunsParameterData
Instances of this class are sent to the initiator in response to
REPORT LUNS SCSI commands. |
Modifier and Type | Class and Description |
---|---|
class |
CachingModePage
The Caching mode page defines the parameters that affect the use of the data cache by the storage medium.
|
class |
InformationExceptionsControlModePage
INFORMATION EXCEPTIONS CONTROL MODE PAGEs carry information about recent INFORMATION EXCEPTION SCSI errors.
|
class |
LogicalBlockDescriptor
An abstract parent class for LOGICAL BLOCK DESCRIPTORs used by direct-access block devices as part of
ModeParameterList objects. |
class |
LongLogicalBlockDescriptor
A class representing the content of LONG LBA MODE PAREMETER LOGICAL BLOCK DESCRIPTOR fields, which are part of
ModeParameterList objects. |
class |
ModePage
MODE PAGEs are sent in response to successful
MODE SENSE SCSI commands. |
class |
ModeParameterHeader
Instances
ModeParameterHeader are part of ModeParameterList objects and specify the layout and length
of the following non-header fields. |
class |
ModeParameterHeader10
A
ModeParameterHeader sub-class. |
class |
ModeParameterHeader6
A
ModeParameterHeader sub-class. |
class |
ModeParameterList
The mode parameter list contains a header, followed by zero or more block descriptors, followed by zero or more
variable-length mode pages.
|
class |
Page_0FormatModePage
Instances of this class represent MODE PAGEs using the PAGE_0 format.
|
class |
ShortLogicalBlockDescriptor
A class representing the content of SHORT LBA MODE PAREMETER LOGICAL BLOCK DESCRIPTOR fields, which are part of
ModeParameterList objects. |
class |
SubPageFormatModePage
Instances of this class represent MODE PAGEs using the SUB-PAGE format.
|
Modifier and Type | Class and Description |
---|---|
class |
ReadCapacity10ParameterData
READ CAPACITY (10) parameter data is sent in response to a successful READ CAPACITY (10)
SCSI command. |
class |
ReadCapacity16ParameterData
READ CAPACITY (16) parameter data is sent in response to a successful READ CAPACITY (16)
SCSI command. |
class |
ReadCapacityParameterData
READ CAPACITY parameter data is sent in response to a successful READ CAPACITY (10) or
READ CAPACITY (16) SCSI command and is mainly used to inform the initiator about the number and length
of the unit's logical blocks. |
Modifier and Type | Class and Description |
---|---|
class |
AdditionalSenseBytes
In additional to the fixed fields that are part of both fixed format and descriptor format sense data, additional
data can be included in the optional ADDITIONAL SENSE BYTES field.
|
class |
DescriptorFormatSenseData
Instances of this class represent sense data using the descriptor format.
|
class |
FixedFormatSenseData
Instances of this class represent sense data using the fixed format.
|
class |
SenseData
Sense data shall be returned in the same I_T_L_Q nexus transaction as a CHECK CONDITION status and as parameter data
in response to the REQUEST SENSE command.
|
Modifier and Type | Class and Description |
---|---|
class |
EightByteInformation
Information with a field length of 8 bytes. |
class |
FourByteInformation
Information with a field length of 4 bytes. |
class |
Information
The contents of the INFORMATION field are device-type or command specific and are defined in a command standard.
|
Modifier and Type | Class and Description |
---|---|
class |
CommandSpecificSenseDataDescriptor
The command-specific information sense data descriptor provides information that depends on the command on which the
exception condition occurred.
|
class |
InformationSenseDataDescriptor
The information sense data descriptor provides information that is device-type or command specific and is defined in
a command standard.
|
class |
SenseDataDescriptor
Sense data descriptors are part of sense data and provide specific sense information.
|
class |
SenseKeySpecificSenseDataDescriptor
The sense key specific sense data descriptor provides additional information about the exception condition.
|
Modifier and Type | Class and Description |
---|---|
class |
ActualRetryCountSenseKeySpecificData
Actual retry count sense-key-specific data is used to communicate the number of retries of the recovery algorithm
used in attempting to recover an error or exception condition.
|
class |
FieldPointerSenseKeySpecificData
Field pointer sense-key-specific data is used to indicate that a certain field of a received command descriptor block
contained an illegal value.
|
class |
InvalidSenseKeySpecificData
This kind of sense-key-specific data can be used instead of all the other
SenseKeySpecificData subclasses, if
no valid sense-key-specific data is to be transmitted to the SCSI initiator. |
class |
ProgressIndicationSenseKeySpecificData
Progress indication sense-key-specific data is used to communicate the progress of a previously issued SCSI command
(e.g.
|
class |
SegmentPointerSenseKeySpecificData
Segment pointer sense-key-specific data is to be used, when the sense key of the enclosing
SenseData has the
value SenseKey.COPY_ABORTED . |
class |
SenseKeySpecificData
SENSE-KEY-SPECIFIC DATA further defines the reason for a CHECK CONDITION SCSI response status.
|
Copyright © 2013 University of Konstanz, Distributed Systems Group. All Rights Reserved.