I interrupted sync --pre-hash at about 80% done. On restart, it went back to 0. A previous interruption at < 1% restarted correctly. I have a lot of data (66TB, 512 blocksize) so the % done had overflowed and only showed 20%. Any ideas? I no longer have the content files, so I can't debug it and I hope to never have to do a full sync again (ETA 75hr).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The "% completed" # is for this invocation of SnapRAID (not a % of the total array). It always starts at 0%.
[As the first step of each command's processing, SR calculates countmax to account for that # of array-blocks actually involved (enabled) for this run.]
Since you wrote "I interrupted ..." (vs sys_crash/power_fail), SR caught the signal/interrupt and performed the requisite housekeeping (writing then-current content_files, etc) before exit. Hence, upon your restart, SR "started" where it/you left off.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I interrupted sync --pre-hash at about 80% done. On restart, it went back to 0. A previous interruption at < 1% restarted correctly. I have a lot of data (66TB, 512 blocksize) so the % done had overflowed and only showed 20%. Any ideas? I no longer have the content files, so I can't debug it and I hope to never have to do a full sync again (ETA 75hr).
The "% completed" # is for this invocation of SnapRAID (not a % of the total array). It always starts at 0%.
[As the first step of each command's processing, SR calculates
countmaxto account for that # of array-blocks actually involved (enabled) for this run.]Since you wrote "I interrupted ..." (vs sys_crash/power_fail), SR caught the signal/interrupt and performed the requisite housekeeping (writing then-current content_files, etc) before exit. Hence, upon your restart, SR "started" where it/you left off.