Bob Proulx wrote:
Christian Franke wrote:
This is logged as LOG_INFO and no sign of trouble. Tracking of
self-test and offline data collection status was added in 5.40 and
5.41 and is enabled by default (-l selftest, -a).
I don't understand. The log message says that the action was
suspended and aborted by an interrupting command. The report in such
a way certainly makes it appear as if an error is occurring.
The message texts are aligned with ATA standards, see T13 documents.
I think
you are saying that this has always been happening but is simply being
reported in this version when it wasn't being reported before. Is
that right?
Yes.
But it still seems like an error, right?
No.
This message is logged as LOG_INFO. Please note that smartd uses
LOG_CRIT level to indicate possible disk problems. This would only be
the case for the "offline data collection was aborted by the device with
a fatal error" state.
Smartmontools 5.42 adds new directives -l selfteststs (included in -a)
and -l offlinests (not included in -a) to control this separately.
Sorry but I don't understand what you are trying to tell me about
using those options. I think you are suggesting that I should add one
of those options to avoid the default of '-l selftest -a'. Is that
right?
Old (5.41) behavior:
'-l selftest' also reports changes of self-test and offline data
collection status.
'-a' includes '-l selftest'.
New (5.42) behavior:
'-l selfteststs' reports changes of self-test execution status.
'-l offlinests' reports changes of offline data collection status.
'-l selftest' does no include the above.
'-a' includes '-l selftest -l selfteststs' but not '-l offlinests'.
See smartd.conf man page.
Conclusion: This bug could be set to fixed.
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
