Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • 1
    "The man page is unfortunately misleading about this. I also verified this with strace" Did you strace the remote, running rsync process or the local one? There are two... one runs on the destination, even when you use ssh. Commented May 6, 2013 at 19:20
  • 18
    There is no post-copy verification for any copies, local or remote. You run rsync -c again if you want to force it to check. Commented May 6, 2013 at 23:50
  • 3
    The verification is done on the incoming stream as it goes. It's not necessary to read it back from the disk if the filesystem has confirmed it's been written. Commented Jul 11, 2018 at 15:51
  • 1
    rsync man page states "Note that rsync always verifies that each transferred file was correctly reconstructed on the receiving side by checking a whole-file checksum that is generated as the file is transferred." Commented Feb 22, 2020 at 12:54
  • @openCivilisation, it looks correct, but so what? I myself got confused with that "receiving side" wording, just wrote an answer here for future reference. Commented Feb 9, 2022 at 4:09