Hmm, don't see a copy of the follow-up message anywhere. Sent to the bug
and not me?
6 devices are being monitored, they're behind a HP controller (cciss
driver).
I don't know for certain that triggering self-tests is the cause, this is
merely obvious speculation. My most recent observations se
smartd.conf file ?
If DEVICESCAN is used: How many devices are detected ?
Triggering self-tests should not require any additional memory as the
actual tests are handled by drive firmware.
Regards,
Christian
smartmontools.org
Package: smartmontools
Version: 6.6-1
`smartd` is doing some sort of activity which tends to trigger the kernel
oom-killer. I suspect this may relate to triggering self-tests.
System in question has plenty of swap available, and presently reports
more than 50MB of available memory.
Presently ad
3 matches
Mail list logo
