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.
Arguably, any message that should be disregarded shouldn't be logged in the first place; should we simply suppress (unless some option is turned on to display them - probably some option less crude than cranking the "syslog" level up so it logs stuff at "debug" level, which causes tons of crap to be logged) messages that are either never significant or that haven't occurred often enough to be significant?
ARGHHHHH!!!!!! Any message is significant, the error history of a device/bus/system is VERY important. Drives that generate a soft (recoverable) error every so often are expected (we have one that's been doing it for years). Drives that have never had any sort of errors that start to produce errors are suspect. Changes in behaivior indicate that something has changed and needs to be looked at.
Hiding minor errors leads to end users living in Cloud-Cuckoo land, "Everything is fine, nothing can go wrong<click>wrong<click>wrong."
Please don't hide this message also (as you supressed the Disk soft error message).
----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Finger for public key scw@cirrus.seas.ucla.edu,Internet mail:scw@SEAS.UCLA.EDU