Leifi Plomeros

If I do change the sub-second timestamps, will the resulting files have their parity re-calculated, as if the file contents had changed? Snapraid touch command modifies the time stamps of the data files and modifies the content file accordingly. In other words: Snapraid diff should not consider the files to have been modified after the touch operation and there should be no need to recalculate the parity. Considering the huge amount of files involved, you may still want to consider a small scale...

If I do change the sub-second timestamps, will the resulting files have their parity re-calculated, as if the file contents had changed? Snapraid touch command modifies the time stamps of the data files and modifies the content file accordingly. In other words: Snapraid diff should not consider the files to have been modified after the touch operation and there should be no need to recalculate the parity. Considering the huge amount of files involved, you may still want to consider a small scale...

If I do change the sub-second timestamps, will the resulting files have their parity re-calculated, as if the file contents had changed? Snapraid touch command modifies the time stamps of the data files and modifies the content file accordingly. In other words: Snapraid diff should not consider the files to have been modified after the touch operation and there should be no need to recalculate the parity. Considering the huge amount of files involved, you may still want to consider a small scale...

I can't see anything wrong and sync is doing progress. So I guess you should simply run sync again to let it finish and then pay extra attention on diff and status for the next few syncs.

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention to what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention to what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

Something definitely went wrong. I would recommend to press CTRL + C to stop current sync and pay close attention what happens. Expected output: bla bla interrupted bla bla Saving state to content files bla bla bla verifying content files bla bla bla Everything OK Verify that above happened as expected. Then run snapraid status to confirm that progress % is around what would be expected for the amount of time it has been running. run snapraid diff to confirm that, from snapraids perspective, nothing...

using sudo snapraid --conf /etc/snapraidNA2.conf list does not show me what disk # the files are on You can add this parameter to see full path in list: --test-fmt path