I didn't seem to get an answer here. How would I know that the 4G wav-file I sent from one box to another is 100% identical?
If we assume (and I think that is what you seem to claim) that we can't blindly trust hashing, but we will assume that no cosmic rays nor hard-drive bit failures can affect the contents, then after I rsync a file from left to right, I would want to _know_ that rsync didn't go cheap on me and sent me the wrong parts just because the rolling checksums and hashes seemed to match. So how do you propose I verify this? 2013/9/20 Janne Johansson <icepic...@gmail.com> > 2013/9/20 <hru...@gmail.com> > >> Janne Johansson <icepic...@gmail.com> wrote: >> >> > In practical terms, if I rsync a file from X to Y, and rsync says it is >> > complete, how to verify the 4G files actually are equal? >> > Given that rsync only knows that hash(A) was equal to hash(B) at the >> end, >> > what do you propose to use for verification? >> >> In practical terms, it is indeed very unprobable that a file that >> passed the last check is not the right one. >> > > Yes, but how to verify it? > > > -- > May the most significant bit of your life be positive. > -- May the most significant bit of your life be positive.
