[RFC] periodic self-tests on short-uptime machines

Lukasz Stelmach <[email protected]> Sat, 01 Nov 2014 10:05:37 +0100

Newsgroups	gmane.linux.utilities.smartmontools
Message-ID	<[email protected]>

Hi.

The way `-s' directive in smartd.conf works is good for long-running
machines but somewhat inappropriate for desktops or laptops which may be
turned on and off and suspended quite often. This is the very same issue
that lead to development of special scripts that run daily (weekly,
monthly) cron jobs and save timestamps across reboots.

SMART self-test logs have the POH-based timestamps and smartd could
trigger the tests at specified intervals: e.g. every 100 power-on-hours.
I admit the implementation may not be as easy as it seems due to
differences in firmware (e.g. my OCZ SSD supports only xselftest and
Seagate HDD has selftest one).

Another problem issue is keeping the machine "alive" until a self-test
is over. It is where Inhibitor Locks[1] might be useful.

RFC.

[1] http://www.freedesktop.org/wiki/Software/systemd/inhibit/

Kind regards,
-- 
Było mi bardzo miło.                   Twoje oczy lubią mnie
>Łukasz<                                     i to mnie zgubi  (c)SNL

REKLAMA: http://ars-fabrica.eu/ sklep z rękodziełem

------------------------------------------------------------------------------

_______________________________________________
Smartmontools-support mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/smartmontools-support

signature.asc (application/pgp-signature, 538 B)