View Single Post
  #6  
Old 12-29-2006, 11:10 PM
trevyn trevyn is offline
Registered User
 
Join Date: Sep 2006
Posts: 10
Quote:
Originally Posted by dnanian View Post
It's likely that the source file was damaged when we read it, but a subsequent write (which is typically done by writing a new file, deleting the old and renaming) was fine.

The actual file copy itself is done with a very well tested atomic OSX call that's relied upon by the entire system...
Maybe, but there's still a problem here in that a subsequent backup is not detecting the file as changed.

Also, I'm having trouble figuring out how "/Applications/SuperDuper!.app/Contents/Resources/Copy Scripts" could end up in any legitimate copy of the file, damaged or not.
Reply With Quote