Any message is significant,
A significant message shouldn't be disregarded.
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.
Which means that logging recoverable errors in the messages file, by itself, may not be what's wanted; what's wanted may be
1) a log you *can* get at, if you want, showing the full history;
2) something that detects a significant increase in the number of recoverable errors, i.e. "[a change] in behavior", and starts yelling and screaming when that happens (heck, perhaps it should, if you have a spare, *fail the drive* once the recoverable error rate goes above a certain level).