Scheduled scrub didn't happen

[scurrier]

On a lark I checked the last scrub time on my pools today and found that, despite being set to 28 days threshold, they had not been scrubbed since Feb 4th. I'm not sure what more details I can provide to help.

I searched the bug tracker and found these:
https://bugs.freenas.org/issues/21506
https://bugs.freenas.org/issues/20230
...but I'm not sure that either quite matches.

I'm on FreeNAS-9.10.2-U2, but I might have been on U1 at the time of the expected scrub. I pretty much update immediately.

 

[dlavigne]

It wouldn't hurt to add a comment to #20230 that you are also experiencing this on U2. Perhaps that can help to push it up to 9.10.3 as it's currently slated for the release after that (9.10.4).

 

[scurrier]

Thanks, done.

 

[cobrakiller58]

It wouldn't hurt to add a comment to #20230 that you are also experiencing this on U2. Perhaps that can help to push it up to 9.10.3 as it's currently slated for the release after that (9.10.4).

Isn't this bug actually user error? If they change the threshold to 20 days it will run on the scheduled days as long as the unit is powered on? and if it is off on the scheduled day it will run on the 20th day after the last scrub then resume it's schedule? or am i misunderstanding this setting.

 

[echelon5]

Isn't this bug actually user error? If they change the threshold to 20 days it will run on the scheduled days as long as the unit is powered on? and if it is off on the scheduled day it will run on the 20th day after the last scrub then resume it's schedule? or am i misunderstanding this setting.

I understood it like in the following example:

I set up a scrub schedule on the 1st, 5th and 15th of the month with threshold days 10.

- a scrub runs on the 1st
- on the 5th, no scrubs will run because it didn't hit the 10 days threshold
- on the 15th another scrub will run because it hit both the threshold and the set day of month
- the next scrub will run on the 1st the next month
- if the NAS is offline on the 1st of the month, the scrub will run on the 5th

At least that's how I saw it work till the bug.

 

[Ericloewe]

Tasks are run iff:

• The threshold was met (or exceeded, perhaps, I'm not sure) AND
• The current date and time has been marked for the task to run.

 

[echelon5]

Tasks are run iff:

• The threshold was met (or exceeded, perhaps, I'm not sure) AND
• The current date and time has been marked for the task to run.

Yes, but in my case they run if the threshold was met. period. I've filed a bug report a while ago and I hope it gets fixed in 11.1.

 

[Ericloewe]

That's definitely a bug (or a feature, in some cases!).