Scrub task is ignoring threshold days
Description
Steps to Reproduce
Expected Result
Actual Result
Environment
Hardware Health
Error Message (if applicable)
Attachments
- 11 Nov 2024, 02:15 PM
Activity
Terry Sposato November 11, 2024 at 2:15 PM
This is also happening for me:
scan: scrub repaired 0B in 12:51:21 with 0 errors on Mon Nov 11 15:51:21 2024
scan: scrub in progress since Tue Nov 12 01:00:01 2024 3.49T / 42.4T scanned at 7.36G/s, 540G / 42.4T issued at 1.11G/s 0B repaired, 1.24% done, 10:41:33 to go
This is my setting:
root@truenas[~]# cat /etc/cron.d/middlewared | grep data 0 1 * * * root PATH="/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin:/root/bin" midclt call pool.scrub.run data 14 > /dev/null 2> /dev/null
So I’m guessing there is something wrong with the task itself.
I am also on TrueNAS-13.3-RELEASE
TrueNAS-13.3-RELEASE
TrueNAS-13.3-RELEASE
Bug Clerk September 10, 2024 at 2:10 PM
This issue has now been closed. Comments made after this point may not be viewed by the TrueNAS Teams. Please open a new issue if you have found a problem or need to re-engage with the TrueNAS Engineering Teams.
Bug Clerk September 10, 2024 at 2:08 PM
Bonnie Follweiler September 10, 2024 at 1:01 PM
Good Morning @Davide Laezza.
I have moved this ticket into our queue to review.
An engineering representative will update with any further questions or details in the near future.
Davide Laezza September 10, 2024 at 6:25 AM
debug and screnshot uploaded via secure file transfer. Thanks
Hi, seems that in my system, somehow, scrub scheduled task ignoring the threshold days and perform scrub on all pool at every “fire trigger”.
The setup is pretty simple, see image attached below.