On Tuesday, November 13, 2007 3:04 PM, Chris Friesen wrote: > > Chris Friesen wrote: > > > We recently moved from 2.6.10 to 2.6.14 and now we're > seeing occasional > > QUEUE_FULL/SAM_STAT_TASK_SET_FULL errors being returned to > userspace. > > These didn't ever show up in 2.6.10. > > I found something that might be interesting. > > With the the 3.01.18 fusion driver the queue length (as shown by > "/sys/class/scsi_generic/sgX/device/queue_depth") was set to 7, while > with the 3.02.57 fusion driver it was set to either 64 or 32. > > It may be coincidence, but it's interesting that > MPT_SCSI_CMD_PER_DEV_LOW is set to 7 in the earlier driver, and 32 in > the later one, while MPT_SCSI_CMD_PER_DEV_HIGH went from 31 to 64. >
QUEUE_FULL and SAM_STAT_TASK_SET_FULL are not errors. SAM_STAT_TASK_SET_FULL returned for the target that handle the number of commands, and QUEUE_FULL returned from hba firmware meaning its can't handle the number of commands. Translated, the commands are retried by scsiml. I probably should be calling scsi_track_queue_full which would be throttling the command back, however I'm not sure whether it matters. Eric - 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