Overlapped command error handling
Subsystems (2)
Hi all,
and here is something for the SCSI Gods out there:
my IOMEGA Zip drive is going into error handling upon access. Surprisingly enough, the device recovered so it's not really critical. However, I wonder whether the error recovery is really a hardware error on the driver itself or whether it's again this blasted aic79xx driver.
What happens is the following:
sd 4:0:6:0: send 0xffff810076858dc0 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 00 00 00 08 00
-> Read some bytes, ok.
sd 4:0:6:0: send 0xffff810076858488 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 08 00 00 38 00
-> send request to read some more bytes, ok. Note that the previous
request has not returned (yet).
sd 4:0:6:0: done 0xffff810076858488 RETRY 8000002 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 08 00 00 38 00
sdb: Current: sense key: Aborted Command
Additional sense: Overlapped commands attempted
-> this _looks_ like an error on the drive as the commands do not really
overlap. It looks more as if the device can't handle more than one command at a time. Do we have a blacklist flag for such things?
sd 4:0:6:0: send 0xffff810076858488 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 08 00 00 38 00
-> Command requeued, okay.
sd 4:0:6:0: done 0xffff810076858488 SUCCESS 0 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 08 00 00 38 00
-> command finished, okay.
sd 4:0:6:0: done 0xffff810076858dc0 TIMEOUT 0 sd 4:0:6:0:
command: Read (10): 28 00 00 00 00 00 00 00 08 00
-> First command was still out there, but appearently never returned.
So of course error recovery started for this command.
It looks to me as if the device has aborted _both_ commands when returning the 'overlapped commands attempted' sense. Is that conformant behaviour?
SCSI-2 states in section 7.5.2:
A target that detects an incorrect initiator connection shall abort all I/O processes for the initiator on the logical unit or target routine and shall return CHECK CONDITION status. The sense key shall be set to ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED COMMANDS ATTEMPTED.
So the behaviour of the drive seems to be okay; however, the scsi stack doesn't abort all commands (yet).
Might that be an error in the scsi stack?
Curious,
Hannes
Signature · 9 lines
Dr. Hannes Reinecke [email protected] SuSE Linux Products GmbH S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 10 lines · Hannes Reinecke
It looks to me as if the device has aborted _both_ commands when returning the 'overlapped commands attempted' sense. Is that conformant behaviour?
SCSI-2 states in section 7.5.2:
A target that detects an incorrect initiator connection shall abort all I/O processes for the initiator on the logical unit or target routine and shall return CHECK CONDITION status. The sense key shall be set to ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED COMMANDS ATTEMPTED.
Actually, I think it's probably complaining about tag reuse in the sense of SAM-3 section 5.9.3. You return this sense if an initiator attempts to use a duplicate tag. Since the aic79xx manges its own tags, then it's probably a driver error. You could verify this by having the aic79xx print out the tag as it sends the command out on the wire. (The device does support TCQ, doesn't it?)
James
Quoted 12 lines · James Bottomley
Quoted 10 lines · Hannes Reinecke
It looks to me as if the device has aborted _both_ commands when returning the 'overlapped commands attempted' sense. Is that conformant behaviour?
SCSI-2 states in section 7.5.2:
A target that detects an incorrect initiator connection shall abort all I/O processes for the initiator on the logical unit or target routine and shall return CHECK CONDITION status. The sense key shall be set to ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED COMMANDS ATTEMPTED.
Quoted 7 lines
Actually, I think it's probably complaining about tag reuse in the sense of SAM-3 section 5.9.3. You return this sense if an initiator attempts to use a duplicate tag. Since the aic79xx manges its own tags, then it's probably a driver error. You could verify this by having the aic79xx print out the tag as it sends the command out on the wire. (The device does support TCQ, doesn't it?)
Argl. Been bitten by the classical 'I know better than thou' attitude.
drivers/scsi/aic7xx/aic79xx_osm.c:ahd_platform_set_tags()
default:
/*
* We allow the OS to queue 2 untagged transactions to
* us at any time even though we can only execute them
* serially on the controller/device. This should
* remove some latency.
*/
but as we also removed the aic7xxx internal timeout handling this means that the queue_depth is always '2', hence the midlayer might attempt to send two command simultaneously to the device.
Which is what it did in my case. And, surprisingly enough, setting the queue depth for the non-TCQ case to '1' fixed the issue.
Can someone explain to my how having a queue depth of '2' in the non-TCQ case can be correct?
If not, please apply the following patch. Oh, and aic7xxx suffers from the same problem, naturally.
Cheers,
Hannes
Signature · 4 lines
Dr. Hannes Reinecke [email protected] SuSE Linux Products GmbH S390 & zSeries Maxfeldstraße 5 +49 911 74053 688 90409 Nürnberg http://www.suse.de
drivers/scsi/aic7xxx/aic79xx_osm.c +5 -15
@@ -1346,25 +1346,15 @@ ahd_platform_set_tags(struct ahd_softc *switch ((dev->flags & (AHD_DEV_Q_BASIC |AHD_DEV_Q_TAGGED ))) {case AHD_DEV_Q_BASIC : -scsi_adjust_queue_depth (sdev, -MSG_SIMPLE_TASK , - dev->openings + dev->active); +scsi_set_tag_type (sdev,MSG_SIMPLE_TASK ); +scsi_activate_tcq (sdev, dev->openings + dev->active);break ;case AHD_DEV_Q_TAGGED : -scsi_adjust_queue_depth (sdev, -MSG_ORDERED_TASK , - dev->openings + dev->active); +scsi_set_tag_type (sdev,MSG_ORDERED_TASK ); +scsi_activate_tcq (sdev, dev->openings + dev->active);break ;default : -/* -* We allow the OS to queue 2 untagged transactions to -* us at any time even though we can only execute them -* serially on the controller/device. This should -* remove some latency. -*/ -scsi_adjust_queue_depth (sdev, -/*NON-TAGGED*/ 0 , -/*queue depth*/ 2 ); +scsi_deactivate_tcq (sdev,1 );break ; } }
Quoted 4 lines · Hannes Reinecke
Can someone explain to my how having a queue depth of '2' in the non-TCQ case can be correct?
If not, please apply the following patch. Oh, and aic7xxx suffers from the same problem, naturally.
Yes, the driver is supposed to be counting both the tagged and untagged commands outstanding and return SCSI_MLQUEUE_DEVICE_BUSY if the mid-layer tries to queue over that.
The premise of setting this to 2 is that we always have one command in progress and one completely prepared ready to fire as soon as the in-progress one returns. Jens has postulated that this is no-longer necessary; we could simply reduce the queue depth to 1 for the non-TCQ case. What this would do is transfer the setup work from the sending process to the block softirq, so it might increase latency in the non-TCQ case ... but no-one knows for sure.
James