"Ethan" == Ethan Torretta ethantor@corp.webtv.net writes:
Ethan> How would you characterize the severity of the message, though? I'm Ethan> inclined to take small numbers of recoverable errors as normal Ethan> operation, but I work in a company with a very noisy monitoring team Ethan> that escalates every single error to completion, often to me. As a Ethan> result it pays to be able to state firmly whether they should Ethan> disregard certain errors (assuming a certain threshold for Ethan> frequency, etc.). The timeout/reset error in particular seems Ethan> harmless but, with more than twenty netapps in use, occurs just Ethan> often enough to be irritating.
In general, an occasional timeout should not be something to lose sleep over. Some of the more common causes of timeouts include
(1) In FC configurations, a bit flip in an FC frame results in the frame being dropped (all frames are CRC protected, so a CRC mismatch will result in the corresponding frame being discarded) leading to a timeout. (2) A disk drive is doing "deep" recovery on a marginally written sector, heroically attempting to recover the data by doing many retries.
Hope this helps,