On Mon, 17 May 1999, Radek Aster wrote:
Wed May 12 00:13:03 EDT [isp2100_timeout]: 8.45 (cmd opcode 0x28, retry count 0): command timeout, aborting request Wed May 12 00:13:03 EDT [isp2100_timeout]: isp2100_reset_device: device 8.45 (1.45)
The above message sequence is a symptom of SCSI command timeout. As part of timeout recovery, the device in question is reset and all pending commands are reissued.
How would you characterize the severity of the message, though? I'm inclined to take small numbers of recoverable errors as normal operation, but I work in a company with a very noisy monitoring team that escalates every single error to completion, often to me. As a result it pays to be able to state firmly whether they should disregard certain errors (assuming a certain threshold for frequency, etc.). The timeout/reset error in particular seems harmless but, with more than twenty netapps in use, occurs just often enough to be irritating.
ejt