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

Lukasz Stelmach wrote:
> 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.

Try -s PREFIX command line option to enable state persistence. Then 
tests "forgotten" during downtime will be started after second(!) device 
polling. See section starting with "If the scheduled tests are used in 
conjunction with state persistence ..." on smartd.conf man page.


> 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).

Yes, and some self-test logs are broken (e.g. on some Intel SSDs). 
Therefore this will probably never be implemented that way.


> 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/

Thanks for the info.

Christian


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