On Sat, 2006-07-01 at 18:56 -0400, Jeff Garzik wrote:
> On Sun, Jul 02, 2006 at 08:32:28AM +1000, Neil Brown wrote:
> > The problem seems to be simply that on some hardware at least,
> > BIO_RW_BARRIER writes result in an EIO. Don't know why yet.
>
> Could be that <whatever device> is choking on FLUSH CACHE (ATA)
> or SYNCHRONIZE CACHE (SCSI).
>
> That's one possible reason why EIO may result from a barrier...
There is no barrier implementation on SCSI (basically you can't maintain
barriers in the face of TCQ, so only depth one devices can do it and
hence all the scsi drivers turn it off), so it must be a FLUSH CACHE.
This one looks like it went down via prepare_flush rather than
issue_flush, so the normal error printing case that issue flush has is
skipped. This patch should tell us what the error was on the command.
James
diff --git a/drivers/scsi/scsi_lib.c b/drivers/scsi/scsi_lib.c
index 3d04a9f..3e3e3b7 100644
--- a/drivers/scsi/scsi_lib.c
+++ b/drivers/scsi/scsi_lib.c
@@ -1162,7 +1162,20 @@ static int scsi_issue_flush_fn(request_q
static void scsi_blk_pc_done(struct scsi_cmnd *cmd)
{
+ int res = cmd->result;
+ struct scsi_sense_hdr sshdr;
+
BUG_ON(!blk_pc_request(cmd->request));
+ if (!res) {
+ printk(KERN_ERR "REQ_BLOCK_PC FAILED for ");
+ __scsi_print_command(cmd->cmnd);
+ printk(KERN_ERR "FAILED\n status = %x, message = %02x, "
+ "host = %d, driver = %02x\n ",
+ status_byte(res), msg_byte(res),
+ host_byte(res), driver_byte(res));
+ if (scsi_command_normalize_sense(cmd, &sshdr))
+ scsi_print_sense_hdr("sd", &sshdr);
+ }
/*
* This will complete the whole command with uptodate=1 so
* as far as the block layer is concerned the command completed
James
-
: send the line "unsubscribe linux-scsi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
