Eric Youngdale wrote: > > Well hosts that don't use the new EH code don't handle QUEUE_FULL. Not > quite sure what would happen with it, actually. > > If everything goes according to plan, when the device returns > QUEUE_FULL, the io should get stuck back in the queue to be handled later. > In addition a flag should be set to prevent further I/O from being sent to > that device - that flag should be cleared when one of the existing I/O > requests actually completes. > > I am not completely sure how best to debug this. I guess the first > thing to do is to see if in fact the QUEUE_FULL is being handled as I > described and the flag is getting set. Then the next thing to look for is > to see what happens when some other I/O finishes. Please note that while another command completing is enough to trigger the next command to be sent, there are cases when we can get a QUEUE_FULL with 0 commands active on the device, resulting in a hung drive if you don't implement a timeout for the paused queue. -- Doug Ledford <[EMAIL PROTECTED]> http://people.redhat.com/dledford Please check my web site for aic7xxx updates/answers before e-mailing me about problems - To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to [EMAIL PROTECTED]
