#4
|
||||
|
||||
It's possible that, if the drive filled "outside" the image, and the image didn't report an error -- or one of the internal OSX copying APIs indicated success on a retry, even though it failed -- then the written files would be damaged. But we wouldn't continue unless OSX itself told us the copy was successful.
No question, though, having insufficient space for your image to grow is unwise: as I mention in the User's Guide, all sorts of catastrophic things can happen if an image is prevented from growing (including kernel panics).
__________________
--Dave Nanian |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
New to Mac and to SuperDuper - Need a little help | MikeG | General | 15 | 02-14-2008 10:35 PM |
Is SuperDuper blowing away a folder? | ChrisC | General | 3 | 09-18-2006 04:59 PM |
SuperDuper Failing on Backup - I/O Errors | Stephen Kuhn | General | 1 | 08-13-2006 04:03 PM |
SuperDuper Backup of AES 128 Encrypted Disk Image | rwg4 | General | 3 | 11-30-2005 10:28 AM |
(Zero-length) File caused SuperDuper to abort backup | alancfrancis | General | 7 | 08-31-2005 10:42 AM |