garoomph |
09-28-2011 05:28 AM |
After verifying a disk image the inode of the file and UUID of the volume are written to an extended attribute. So merely opening a DMG on the target makes it different in the eyes of SuperDuper.
This is unfortunate as I like the checksum of compressed images to alert me to hardware failure. A workaround is locking the DMG to prevent the attribute from changing, but then the image is verified each time you open it.
Does SD already special-case some metadata? If so, how about ignoring com.apple.diskimages.recentcksum? If it doesn't make things too slow.
The above doesn't explain why my locked images are still copied, but I'm fed up with experiments that take hours. Is there a dry-run mode in the command line version of SD?
|