Closed jshank closed 2 years ago
Scrub will throw errors if the docker containers make any changes to files that are being scrubbed.
For scrub
, SnapRAID manual says the following:
This command verifies the data in your array comparing it with the hash computed in the "sync" command.
So I agree with @tehniemer, since scrub is actually comparing hash with the real data.
Is better to have everything paused/stopped as long as SnapRAID commands are running.
You could consider the "SCRUB_DELAYED_RUN" feature to run scrubs only every once in a while, or reducing scrub percentage/age.
I always welcome contributions, but let's try to stick to SnapRAID best practices!
Closing this issue.
I wanted to minimize the pause duration of my docker containers so I moved the Resume paused containers section of the script before the SCRUB is done. Is there a benefit to having them paused for the SCRUB? Happy to do a PR if that makes sense.