Update to myself: When I return SUCCESS to the spurious ABORTs, the systems keeps running. I am getting aborts for commands that I completed as early as 60+ seconds ago. Could somebody please tell me what in SCSI layer can cause it to do this? Thanks, Sreenivas > >I am running rather heavy IO's on our MegaRAID controller on a >Red Hat 3.0 Gold (2.4.21-4.Elsmp) 32 kernel. After a while, I >notice that the OS sends the abort requests for commands that >the driver has completed a while ago! I am using the unused >struct scsi_cmnd->SCp fields to record the entry/exit >timestamps and also the status of each commands while it is >being processed. >When I get the abort request, I am seeing that driver had >completed the command already. > >I know that this is not an appropriate list to ask RH specific >question. But I wasn't sure if it RH specific bug or if there >are any known situations where 2.4 based kernels would try to >_abort_ previously completed commands. I tried tracing the >SCSI mid-layer code and I quickly got lost. > - : 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
