On Mon, Jun 14, 2010 at 09:43:28AM +0200, Tejun Heo wrote: > > sd 11:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > > sd 11:0:0:0: [sdd] CDB: Write(10): 2a 00 00 e5 f0 08 00 01 00 00 > > sd 11:0:0:0: [sdd] Unhandled error code > > sd 11:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > > sd 11:0:0:0: [sdd] CDB: Write(10): 2a 00 00 e5 f1 08 00 01 00 00 > > sd 11:0:0:0: [sdd] Unhandled error code > > sd 11:0:0:0: [sdd] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK > > sd 11:0:0:0: [sdd] CDB: Write(10): 2a 00 00 e5 f2 08 00 01 00 00 > > > > same messages repeating forever, just with CDB changing occasionally. > > > > .... > > > > not stopping until I reset the box. > > Did you have a lot of dirty pages? It looks like upper layer is Yes, there was a dd running. > trying to flush all the dirty buffers and SCSI is a tad bit too > verbose about failing each IO w/ DID_BAD_TARGET thus taking a very A bit too verbose? That's really an euphemism ... During the CDB: Write loop the console was totally unusable! And I think the fsyncs in syslogd completely made the performance tank. So basically it was a "reset button only" situation. When the device is gone what's the point in giving a message more than once? Can't the requests just be silently failed in this case? -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
