Opened 6 years ago

Last modified 5 years ago

#310 accepted enhancement

Automatic staggering of drive tests

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

Description

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 (2)

comment:1 Changed 6 years ago by Christian Franke

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 Changed 5 years ago by Christian Franke

Milestone: unscheduled
Note: See TracTickets for help on using tickets.