Bug#974755: smartd: Problematic memory activity (triggers oom-killer)

[Christian Franke]

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

Bug#974755: smartd: Problematic memory activity (triggers oom-killer)

[Elliott Mitchell]

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 adding "choom -p $$ -n +500 >/dev/null" to
/etc/default/smartmontools works around the worst of the damage as this
causes it to tend to kill itself instead of rather more critical daemons.


-- 
(\___(\___(\__  --=> 8-) EHM <=--  __/)___/)___/)
 \BS (| ehem+sig...@m5p.com  PGP 87145445 |)   /
  \_CS\   |  _  -O #include  O-   _  |   /  _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445