FreeNASBob
Patron
- Joined
- Aug 23, 2014
- Messages
- 226
Is there some reason we don't get to set threshold days for SMART tests, only for scrubs?
It's not available for SMART. I'm asking why.is this available for SMART? I'm not sure.. Within the GUI you can be pretty specific when you want the tests to occur.. I found the threshold for scrubs confusing at first..
I can't think of a reason why someone wouldn't want the same flexibility with SMART.It's probably not nescessary for SMART.. Whereas ZFS scrubs you may want some more flexibility depending on schedules..
Smartmontools people write the FreeNAS GUI for scheduling SMART tests? I thought it was just a cron job.The actual place to ask it is from the smartmontools people. They're the ones that would have to add it to their project first.
Cron just executes smartmontool on schedule. There's nothing to communicate to smartmontools except which devices to test. A threshold is a scheduling mechanism, which is cron's domain. All that's required is to limit execution of smartmontools to x days apart. Something like:You are correct, it's just a cronjob. But the user is talking about having thresholds added. That would mean telling smartmontools, when it's run, to obey some threshold.
Cron just executes smartmontool on schedule. There's nothing to communicate to smartmontools except which devices to test. A threshold is a scheduling mechanism, which is cron's domain. All that's required is to limit execution of smartmontools to x days apart. Something like:
0 3 */2 * *
That's precisely what I said above in my first post.
I also tried to explain why the threshold isn't as "important" as people might think it is.
I also tried to explain why the "threshold" and "power-on" isn't quite the same so the theory behind why one has a threshold and one has power-on isn't the same. ;)
Now in my theoretical "how to implement the threshold" you'd add a parameter to the cronjob itself that would tell smartmontools what the 'threshold' would be. Then it would check with the disk's info and make that call. Or, you code your own script to do all this and then simply run that script as a cronjob.
My apologies if I got it wrong. I thought you were trying to say that the best way to schedule SMART tests was to have the smartmontools folks add scheduled automated testing capabilities to their software package.
I'm not sure what relationship "power-on" time has to cron scheduling.
That sounds more like trying to schedule a test based on the amount of time a disk has been spinning. That's independent and unrelated to a threshold number of days between tests.
/dev/ada2 -a -n never -W 5,35,45 -m my@email.com -s L/(01|02|03|04|05|06|07|08|09|10|11|12)/(07|21)/(1|2|3|4|5|6|7)/(02) -a -M daily -R 5! -R 10! -R 187! -R 188! -R 189! -R 197! -R 198! -R 199!
I think you'd have to ask the smartmontools people if you wanted a threshold implemented. I really don't see the need.
Based on all of this I'd expect the smartmontools to say that it's not desirable, but put the ticket in and let them make that call. ;)