Smart Update Failed - Device Full

[ae6dx]

Source HD has 28.81 GB used. Target HD has 37.2 space total. Yet the target is full. Using smart update. Why would this be? If the target has m,ore space than source why is it filling up?

See log below
| 06:43:14 PM | Info | SuperDuper!, 2.1.3 (80), path: /Applications/SuperDuper!.app, Mac OS 10.4.7 build 8J135 (ppc)
| 06:43:14 PM | Info | Started on Sun, Aug 20, 2006 at 6:43 PM
| 06:43:14 PM | Info | Source Drive: Macintosh HD, mount: /, device: TOSHIBA MK6021GAS, interconnect: Internal ATA, file system: "Journaled HFS+", OS: 10.4.7 (8J135), capacity: 55.76 GB, used: 28.81 GB, directories: 74564, files: 327102, ejectable: NO, ACLs: Disabled
| 06:43:14 PM | Info | Target Drive: OS Backup, mount: /Volumes/OS Backup, device: SmartDis FireLite Drive, interconnect: External FireWire, file system: "Journaled HFS+", OS: 10.4.6 (8I127), capacity: 37.20 GB, used: 25.33 GB, directories: 60856, files: 287488, ejectable: NO, ACLs: Disabled
| 06:43:14 PM | Info | Copy Mode : Smart Update
| 06:43:14 PM | Info | Copy Script : Backup - all files.dset
| 06:43:14 PM | Info | Transcript : BuildTranscript.plist
| 06:43:15 PM | Info | PHASE: 1. Prepare to Copy Files
| 06:43:15 PM | Info | ...ACTION: Preparing Macintosh HD
| 06:43:15 PM | Info | ......COMMAND => Verifying the integrity of volinfo.database
| 06:43:16 PM | Info | volinfo.database OK
| 06:43:16 PM | Info | ......COMMAND => Enabling permissions on Macintosh HD
| 06:43:16 PM | Info | Refreshing Disk Arbitration ...
| 06:43:17 PM | Info | ......COMMAND => Verifying that permissions are enabled for Macintosh HD
| 06:43:17 PM | Info | Permissions on '/' are enabled.
| 06:43:17 PM | Info | ...ACTION: Repairing permissions on Macintosh HD
| 06:43:17 PM | Info | ......COMMAND => Repairing permissions on Macintosh HD
| 06:43:31 PM | Info | parent directory ./Users/Shared/SC Info does not exist
| 06:44:40 PM | Info | Started verify/repair permissions on disk disk0s10 Macintosh HD
| 06:44:40 PM | Info | Determining correct file permissions.
| 06:44:40 PM | Info | The privileges have been verified or repaired on the selected volume
| 06:44:40 PM | Info | Verify/repair finished permissions on disk disk0s10 Macintosh HD
| 06:44:40 PM | Info | ...ACTION: Preparing OS Backup
| 06:44:40 PM | Info | ......COMMAND => Enabling permissions on OS Backup
| 06:44:40 PM | Info | Refreshing Disk Arbitration ...
| 06:44:41 PM | Info | ......COMMAND => Verifying that permissions are enabled for OS Backup
| 06:44:41 PM | Info | Permissions on '/Volumes/OS Backup' are enabled.
| 06:44:41 PM | Info | ......COMMAND => Verifying that OS Backup ACL support matches Macintosh HD
| 06:44:41 PM | Info | ...ACTION: Preserving Spotlight state on OS Backup
| 06:44:41 PM | Info | ......COMMAND => Disabling Spotlight search indexing on OS Backup
| 06:44:41 PM | Info | PHASE: 2. Copy Files
| 06:44:41 PM | Info | ...ACTION: Copying files from Macintosh HD to OS Backup using Smart Update
| 06:44:41 PM | Info | ......COMMAND => Cloning Macintosh HD to OS Backup
| 06:44:42 PM | Info | Copying copy files with delete using script: /Users/bradford/Library/Application Support/SuperDuper!/Copy Scripts/Standard Scripts/Backup - all files.dset
| 06:44:43 PM | Info | Loading 19 commands from copy script /Applications/SuperDuper!.app/Contents/Resources/Copy Scripts/Exclude system temporary files.dset
| 06:44:43 PM | Info | Loading 6 commands from copy script /Applications/SuperDuper!.app/Contents/Resources/Copy Scripts/Exclude system cache files.dset
| 06:44:43 PM | Info | Loading 1 commands from copy script /Applications/SuperDuper!.app/Contents/Resources/Copy Scripts/Exclude Norton FileSaver files.dset
| 06:44:43 PM | Info | Loading 2 commands from copy script /Applications/SuperDuper!.app/Contents/Resources/Copy Scripts/Exclude Spotlight search index.dset
| 06:44:43 PM | Info | Loading 0 commands from copy script /Users/bradford/Library/Application Support/SuperDuper!/Copy Scripts/Standard Scripts/Backup - all files.dset
| 06:44:43 PM | Info | /
| 06:44:46 PM | Info | /dev
| 06:44:46 PM | Info | /.Spotlight-V100
| 06:44:46 PM | Info | Ignoring /.Spotlight-V100/.journalHistoryLog
| 06:44:46 PM | Info | Ignoring /.Spotlight-V100/.store.db
| 06:44:46 PM | Info | Ignoring /.Spotlight-V100/_rules.plist
| 06:44:46 PM | Info | Ignoring /.Spotlight-V100/ContentIndex.db
| 06:44:46 PM | Info | Ignoring /.Spotlight-V100/store.db
| 06:44:46 PM | Info | /Network
| 06:44:46 PM | Info | /private
| 06:44:46 PM | Info | Did not COPY shared-item /private/tftpboot/private/tftpboot because it would have overwritten the original
| 06:44:46 PM | Info | Ignoring /private/var/db/volinfo.database
| 06:44:46 PM | Info | Ignoring /private/var/db/BootCache.playlist
| 06:44:52 PM | Info | Ignoring /private/var/run
| 06:44:52 PM | Info | Ignoring /private/var/tmp/ismp001
| 06:44:52 PM | Info | Ignoring /private/var/tmp/mds
| 06:44:52 PM | Info | Ignoring /private/var/tmp/com.netopia.timbuktu.pro.skype.501
| 06:44:52 PM | Info | Ignoring /private/var/tmp/com.netopia.timbuktu.pro.skype.0
| 06:44:52 PM | Info | Ignoring /private/var/tmp/folders.501
| 06:44:52 PM | Info | Ignoring /private/var/tmp/console.log
| 06:44:52 PM | Info | Ignoring /private/var/tmp/com.apple.speech.synthesis.globals
| 06:44:52 PM | Info | Ignoring /private/var/vm
| 06:44:52 PM | Info | /sbin
| 06:44:55 PM | Info | /sw
| 06:45:10 PM | Info | /System
| 06:48:27 PM | Info | Ignoring /System/Library/Extensions.kextcache
| 06:48:27 PM | Info | /.Trashes
| 06:48:27 PM | Info | /TheVolumeSettingsFolder
| 06:48:27 PM | Info | /cores
| 06:48:27 PM | Info | /Users
| 06:50:59 PM | Info | /usr
| 06:51:52 PM | Info | /.vol
| 06:51:52 PM | Info | Ignoring /.vol
| 06:51:52 PM | Info | /Volumes
| 06:51:52 PM | Info | Ignoring /Volumes/BACKUP#1
| 06:51:55 PM | Info | Ignoring /Volumes/FIRE
| 06:51:55 PM | Info | Ignoring /Volumes/OS Backup
| 06:51:55 PM | Info | Ignoring /Volumes/Macintosh HD
| 06:51:55 PM | Info | /Library
| 07:01:18 PM | Info | /Applications
| 07:28:56 PM | Info | WARNING: Caught I/O exception(28): No space left on device
| 07:28:56 PM | Info | WARNING: Source: /Applications/Compressor.app/Contents/Resources/French.lproj/AboutNFR.tif, lstat(): 0
| 07:28:56 PM | Info | WARNING: Target: /Volumes/OS Backup/Applications/Compressor.app/Contents/Resources/French.lproj/AboutNFR.tif, lstat(): 0
| 07:28:56 PM | Info | Attempting to copy file using copyfile().
| 07:28:56 PM | Info | Attempting to copy file using ditto.
| 07:28:57 PM | Error | ditto: /Volumes/OS Backup/Applications/Compressor.app/Contents/Resources/French.lproj/AboutNFR.tif: No space left on device

[dnanian]

Hi, Brad. I've already replied to your support mail, so let me refer you there. (For others, see the Troubleshooting section of the User's Guide for a full discussion of how this happens with Smart Update.)

[Twitch]

I also get this error. Working with video, my files tend to be quite large and they do get moved around. I usually get this error 50-70% of the time I try to mirror two drives of identical size.

There are so many things I love about this program, unfortunately I'm getting tired of comming in to my studio in the morning to find superduper failed to mirror my drive the night before.

Any chance this can be improved in a future release? I used to use psync to mirror my drives from the command line and I don't recall this ever happening.

[dnanian]

We're looking at various ways to improve this in the future, Twitch, yes.

psync didn't have this problem for you because it first runs an erase pass, then it does a copy. The problem with that is it leaves you a lot more vulnerable -- if your drive failed in between, you'd lose both the "backed up" copy and the original, since everything had been deleted...

[Twitch]

ahhh.. I didn't look at it from a vulnerability aspect, makes sense. I guess psync exposes files renamed or moved to potential data loss.

Now I'm a bit more nervous about the suggested work around (erase then copy). This potentialy leaves the entire drive vulnerable for data loss.

I guess this is a no-win situation. I suppose it's best to have a backup drive larger than the orignal for maximum safety and in that case it's good to know SuperDuper will keep the data as safe as possible during the copy operation.

[dnanian]

Alternative workarounds are simply "helping" Smart Update. So, if you've renamed a large folder on the source, do the same on the destination. Then, SD! won't have trouble.

But, as I said, we have some ideas...