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 seem to suggest this is incorrect as the oom-killer was triggered at a time when self-tests shouldn't be run. I'm open to other programs on the system being the actual cause, allocating memory quickly and pushing the limits. Thing is I've never observed any program besides `smartd` triggering the oom-killer. -- (\___(\___(\______ --=> 8-) EHM <=-- ______/)___/)___/) \BS ( | ehem+sig...@m5p.com PGP 87145445 | ) / \_CS\ | _____ -O #include <stddisclaimer.h> O- _____ | / _/ 8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
