#5
|
|||
|
|||
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? |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | Rate This Thread |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Is it possible to create an encrypted disk image file with SuperDuper? | Bob | General | 6 | 04-24-2010 12:16 AM |
Multiple errors of kind: "Caught I/O exception(5): Input/output error" | amagjo | General | 7 | 04-14-2009 10:01 PM |
Cannot Read SuperDuper! Image from Tiger in Leopard | ecornips | General | 2 | 12-11-2007 09:50 PM |
Undersized disk image and a Boot Camp-related backup question | garybollocks | General | 3 | 10-23-2006 01:07 PM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |