El Lunes, 24 de Abril de 2006 17:02, James Bottomley escribió: > On Mon, 2006-04-24 at 16:30 -0500, Gustavo Guillermo Pérez wrote: > > Ok, this is what I've got. > > Thanks, this is interesting: > > Apr 24 16:12:14 gusgus kernel: sr 1:0:0:0: Device not ready: <6>: > > Current: sense key=0x2 > > Apr 24 16:12:14 gusgus kernel: ASC=0x4 ASCQ=0x8 > > That's "LU not ready; long write in progress" > > > This Other is cause I left the print outside the brackets, cause I want > > to see on closing session. > > > > Apr 24 16:13:10 gusgus kernel: : Current: sense key=0x2 > > Apr 24 16:13:10 gusgus kernel: ASC=0x3a ASCQ=0x0 > > Yes, that's just medium not present. > > So, I could change the long write in progress to a retry. However, I > suspect the reason we got that return is because this device is untagged > (doesn't accept multiple commands at once) and perhaps a better fix > might be to reduce the queue depth down to one to prevent more than one > command being outstanding at any one time. It would not be better to include some handling on the black list? it means doing a new BLACK_CONST to handle just this special case?. -- Gustavo Guillermo Pérez Compunauta uLinux www.compunauta.com - : 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
