Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

While my regular backup script was running (using rsync to move files from NFS to external harddrive) we had network problems and I was forced to kill the rsync job in the middle of moving files. Could this have corrupted my files? The job should run again tomorrow and overwrite the current backup, so will those files be good?

share|improve this question
Are you talking about the source or the destination files? Why would either of them not be OK? What rsync command were you using? Which options? – terdon Jul 5 '13 at 23:41
up vote 0 down vote accepted

Generally rsync will create a copy of the file and then move it into place once the copy is done. It is very unlikely to have corrupted a file. It doesn't alter files it is reading. (Although the operating system may update the last accessed timestamp.)

There is an option to update files in place which could cause corruption (inconsistent data) if it was updating a file. I've only used it to copy log files, and configured it to assume the portion of the file already copied wasn't changed.

It is likely you have only a partial backup, with some files backed up and others not. Re-running rsync should just complete the backup.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.