rsync -auIn not doing what I expect (rsync 2.6.3)

Eberhard Moenkeberg emoenke at
Fri Feb 4 23:06:18 GMT 2005


On Fri, 4 Feb 2005, Bart Brashers wrote:

> Some of my files recently became corrupted due to disk I/O errors (bad
> SCSI terminator).  I've fixed my I/O errors, run fsck, and am now
> wanting to restore from my rsync backup.
> However, some time has passed, and users have continued working,
> creating new files, in some cases with the same filename as existed
> before the disk I/O problems started.  E.g. editing a .c file to fix a
> bug.
> Some of the files are corrupt, even though they have the same file sizes
> and timestamps (often years ago) as the backup files.  I've spot-checked
> and confirmed that the backup files are not corrupt.
> Ok, this should be easy, right?  Let's see what would happen:
> rsync -auIn backup:/archive/home /home
> The "-I" tells rsync to ignore the timestamps (the corrupt files still
> have old timestamps) and the file sizes (the corrupt files are the same
> size as the backup non-corrupt files) and do the checksums to determine
> which files need to be transferred.

Why do you want to say "ignore timestamps" if just the "corrected" files 
have newer than the corrupt ones?

Cheers -e
Eberhard Moenkeberg (emoenke at, em at

More information about the rsync mailing list