In the diskio.c, if the scsi command was used, the read or write timeout
error would be more circumstantial. When the read/write timeout occurs, the
scsi command could distinguish the actual reason, io busy, not ready,
hardware error and so on. If the reason was io busy, we can enlarge the
timeout-time for robustness.
What do you think about this?
Appreciate for your reply. Thanks
Sense Key Name Description 0h No Sense Indicates there is no specific
Sense Key information to be reported for the disc drive. This would be the
case for a successful command or when the ILI bit is one. 1h Recovered
Error Indicates the last command completed successfully with some recovery
action performed by the disc drive. When multiple recovered errors occur,
the last error that occurred is reported by the additional sense bytes.
Note: For some Mode settings, the last command may have terminated before
completing. 2h Not Ready Indicates the logical unit addressed cannot be
accessed. Operator intervention may be required to correct this condition.
3h Medium Error Indicates the command terminated with a non-recovered error
condition, probably caused by a flaw in the medium or an error in the
recorded data. 4h Hardware Error Indicates the disc drive detected a
nonrecoverable hardware failure while performing the command or during a
self test. This includes SCSI interface parity error, controller failure or
device failure. 5h Illegal Request Indicates an illegal parameter in the
command descriptor block or in the additional parameters supplied as data
for some commands (Format Unit, Mode Select, and so forth). If the disc
drive detects an invalid parameter in the Command Descriptor Block, it
shall terminate the command without altering the medium. If the disc drive
detects an invalid parameter in the additional parameters supplied as data,
the disc drive may have already altered the medium. This sense key may also
indicate that an invalid IDENTIFY message was received. This could also
indicate an attempt to write past the last logical block. 6h Unit
the disc drive may have been reset. 7h Data Protect Indicates that a
command that reads or writes the medium was attempted on a block that is
protected from this operation. The read or write operation is not performed.
9h Firmware Error Vendor specific sense key. Bh Aborted Command Indicates
the disc drive aborted the command. The initiator may be able to recover by
trying the command again. Ch Equal Indicates a SEARCH DATA command has
satisfied an equal comparison. Dh Volume Overflow Indicates a buffered
peripheral device has reached the end of medium partition and data remains
in the buffer that has not been written to the medium. Eh Miscompare Indicates
that the source data did not match the data read from the medium.
2013/6/7 David Teigland <teigland(a)redhat.com>
On Fri, Jun 07, 2013 at 12:11:46AM +0800, tsiren tsi wrote:
> Hi, all
> I hava read the source code of sanlock some days. But I have a question,
> is that why scsi command was not used in the 'diskio.c'? The scsi command
> can catch much more exception the io.
> Could someone help me?
How would you use a scsi command here?
If we did get more exception information, what would you use it for?
> /* write aligned io buffer */
> int write_iobuf(int fd, uint64_t offset, char *iobuf, int iobuf_len,
> struct task *task, int ioto)
> if (task && task->use_aio == 1)
> return do_write_aio_linux(fd, offset, iobuf, iobuf_len, task,
> else if (task && task->use_aio == 2)
> return do_write_aio_posix(fd, offset, iobuf, iobuf_len, task,
> return do_write(fd, offset, iobuf, iobuf_len, task);