Table 3-6, File-system error codes and their meanings – HP Integrity NonStop H-Series User Manual
Page 32
Interfacing With the Open SCSI I/O Process (IOP)
File-System (FESTATUS) Error-Code Values
Table 3-6. File-System Error Codes and Their Meanings (page 1 of 3)
Error
Code
Corresponding
FESTATUS Literal
Meaning or Error Cause
0
FEOK
No error detected by IOP in command execution.
However, also check the CAM status values (
on page 3-20) and SCSI status values (
2
FEINVALOP
Check for one of these causes:
•
Diagnostic operations had an incorrect buffer
length.
•
A Set/Get Mode operation specified an invalid
mode.
14
FENOSUCHDEV
Check for one of these causes:
•
A request involved a device or path that is not
configured or reachable by the IOP.
•
The IOP received a request for a device that it does
not control.
15
FEWRONGDEV
The wrong LDEV was specified. This error code should
not be returned for normal I/O operations and is
currently returned only for some operations performed
by the Subsystem Control Facility (SCF).
21
FEBADCOUNT
Check for one of these causes:
•
The requested length was too long for the process
type or the I/O subsystem.
•
The buffer length was too short to hold the header
information on a write-read passthrough command.
•
The buffer was too short for the specified transfer
length.
•
The number of bytes transferred to or from the
controller did not match the number requested.
The FEBADCOUNT literal might be returned in cases
where there is no valid buffer status; for example, if the
IOP detecting a buffer is not long enough to contain
even a valid header.
28
FETOOMANY
The IOP cannot process the I/O request at this time.
When an application receives this error code in
response to an operation, it should wait a small amount
of time and retry the operation. The maximum number
of I/O operations the IOP can process at any one time is
specified by the NUMIO attribute of the SCF SCSI
subsystem, and this error occurs if the current operation
would cause the IOP to exceed that number.