WarmongerX

Ok, that explains it. Thanks. I thought it was scrubbing % of the data in the array which is why I wasn't getting what you were trying to convey. % of the parity drives makes more sense now.

Ok, explains it. Thanks. I thought it was scrubbing % of the data in the array which is why I wasn't getting what you were trying to convey. % of the parity drives makes more sense now.

That is correct, but it still doesn't explain why the scrub is scrubbing so much more data compared to before with the same argument of 3%. The actual amount of data in the array hasn't changed more than a few hundred GB on a ~47TB pool.

lol, ok. I'm not sure what I can share. I have the output go to a text file, which is then emailed to me every morning. Normally it takes around 16 minutes to do 3% of the array. After upgrading to the new version it's taking over twice that long at the same speed. I can attach my 2 log files. One new and one old, but it doesn't show that it's doing 3% of the array in either log. It doesn't appear SnapRAID outputs that info. You can see however the amount of data accessed is substantially larger...

I've been running Snapraid for several years and recently upgraded from 11.2 to 11.3. I run the snapraid scrub -p 3 command in a script every morning to only scrub 3% of the array per day. This has worked without issue for some time now. However after upgrading to 11.3 the -p argument no longer seems to be taken in. No matter which way I try to execute the argument, it still does the default of 8%. I tried searching through the forum looking for notes on changes, but didn't find anything related...

Thanks guys. I'm happy to report that the Priority was the culprit. I was unaware...

I've been battling this issue for almost a year now and I thought I had it rectified...

Out of curiousity, what software were you using for SMART monitoring that didn't...