Opened 10 years ago

Closed 3 years ago

Last modified 3 years ago

#310 closed enhancement (fixed)

Support staggering of drive tests

Reported by: weedy2887 Owned by: Christian Franke
Priority: major Milestone: Release 7.2
Component: smartd Version: 6.2
Keywords: smartd.conf Cc:


On the mailing list a best practise thread popped up asking about test cycles which brought us to DEVICESCAN and the staggering of these tests when you have many (4+) drives in a box.

A: If a user feeds something like "(O/../../(7|3)/00|S/../.././12|L/../../6/03|C/../../7/03)" to DEVICESCAN it should use best effort to not send that command to every drive at once. It should probably assume something like +30% of a drives reported test runtime before triggering another drive. OR maybe the schedule is in "every X days" and not "sun-sat" calendar weeks per say.

B: A sane default (one short test per day, one/two long test per week, one offline per week/month?) to be added commented of course to the default config file.

Change History (6)

comment:1 by Christian Franke, 10 years ago

Component: allsmartd
Keywords: smartd.conf added; DEVICESCAN staggering stagger tests removed
Milestone: Release 6.3
Owner: changed from somebody to Christian Franke
Status: newaccepted

comment:2 by Christian Franke, 9 years ago

Milestone: unscheduled

comment:3 by Christian Franke, 3 years ago

Milestone: unscheduledRelease 7.2

comment:4 by Christian Franke, 3 years ago

Resolution: fixed
Status: acceptedclosed

comment:5 by Christian Franke, 3 years ago

Summary: Automatic staggering of drive testsSupport staggering of drive tests

Not actually automatic, because there is no easy way to handle all common cases.

It is configurable in the regexp. With above example:


specifies a five hour delay per drive for Long self-tests and a one hour delay for Conveyance self-tests.

comment:6 by Christian Franke, 3 years ago

With r5118, this regexp:


limits delay for Long self-tests to 23 hours.

Note: See TracTickets for help on using tickets.