Patrick Mansfield wrote:
On Tue, May 16, 2006 at 12:05:19PM -0400, James Smart wrote:
I don't mind making it bigger, especially as this is just a max, not the
default value. I tried to keep it low, as I believe even 2 mins is a long
time from the system's perspective. 10 minutes is forever (and remember
the scan deadlock that we just worked through).
Yes, so add default and max settings instead of using the max as the default.
Agreed - doing so.
And I still don't see how the scsi timeout can (reliably) make it through
these block/unblocks. EH_RESET_TIMER doesn't freeze the scsi timeout like
you really need, just restarts it.
For example, with default sd timeout of 30, you could be one second into a
command, block for 28 seconds, unblock, and then still timeout.
True. However, the point was not necessarily to allow the command to
succeed. Note: any target disappearance for any real amount of time (like 28s)
is likely going to be a condition that required a new login and killed the
i/o anyway.
The rescheduling of the timeout was to avoid the ramifications of the timeout
fails, which it would do, as there's no target to send the abort request to.
What was happening was the abort was failing, the device reset was failing,
and it escalated up to bus resets and adapter resets - followed by a Test Unit
Ready being sent, which of course was to a non-existent target, which failed
and took the device offline. Which then required manual interaction to restart
io.
-- james
-
: 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
