Time Machine doing a full backup every time it runs

My Time Machine seems to be doing a full backup every time it runs on the hour. The backup size is about 19GB. Shouldn't hourly and daily backups be much smaller after you run Time Machine for the first time?
I remember a while back, my hourly backups were a couple of minutes.....now they are 30 minutes.
John

Hi Steve,
http://pondini.org/TM/12.html
https://discussions.apple.com/thread/3687285?start=0&tstart=0
http://pondini.org/TM/Troubleshooting.html

Similar Messages

  • Time machine does a full backup every time I reconnect my portable drive to my macbook pro

    How do I stop time machine from doing a full backup every time I disconnect & reconnect my backup portable drive to my macbook pro. It doesn't recognize the old backups.

    Hi Steve,
    http://pondini.org/TM/12.html
    https://discussions.apple.com/thread/3687285?start=0&tstart=0
    http://pondini.org/TM/Troubleshooting.html

  • Time machine makes a full backup every time

    I had a 1tb external drive that I was using for Time Machine backups. Fine. No problem. But it got filled up.
    I bought a new external drive - 1Tb. Iwas surprised that within a couple of wweeks, it was filled up.
    I bought a new 2Tb drive.
    Now as I observe what it's doing, it appears ot meaking a FULL BACKUP of my entire hard drive over and over again. I though it was only supposed to do incremental backups? This is nuts! At this rate my 2Tb drive will be filled up in no time. And becasue it's continually backing up many Gb of data it makes the machine run slowly. It is driviing me crazy!!! How do I stop this behaviour? Why is it making a full backup every time? I can't see any preferences to change this. Help!

    Thanks but I think maybe I didn't explain the problem clearly
    My understanding is that Time Machine backs up only the fiels that have changed each time it does a backup. Thi sis how it USED to work. So each hourly backup would take a few minutes, usually, and a 1TB drive lasted well over a year.
    Now it seems to be making a FULL backup of the COMPLETE internal drive EVERY HOUR! So it is currently backing up 135Gb of data and my Time Machine drive is almost half full,, even though I only installed it two days ago!
    When it gets to the point where it needs to start deleting old backups, I would get a new drive and start afresh, saving the old one for reference. I can't buuy a new backup drive every week!
    How do I get it to behave like it used to?

  • Time Machine Does Excessive Full Backups

    Time Machine used to just backup changed material on a hourly basis. It seems that recently every time I look at the progress indicator it is trying to do a full backup of my entire hard drive. Any ideas why?

    Have you recently done a restore?
    I have the same problem. I did a full restore, and TM did a full backup afterwards. This is a "documented feature". Then it did skims every hour. However, if I reboot, it does a full backup the first time after the reboot. It's done 5 full backups (50 GB each) in the past 5 days. I can't afford to shut down my Mac until I figure this out. I only have 170GB of free space on my Time Machine drive.
    Is there any way to see how big each backup is, and delete un-needed ones?
    I'd really like to figure out what causes this problem, before Time Machine starts deleting old stuff I want backed up to make room for all these wasteful new backups.

  • Time Machine does a full backup after a full restore

    Hi,
    To test Time Machine (as you should always do with any backup system) I decided to do a full restore of one of my Macs. This went fine (after figuring out how to mount my remote backup disk).
    However I noticed that when the restored machine did its first scheduled Time Machine backup after being restored it did what pretty much amounted to a full backup (taking ages).
    I believe Time Machine should be clever enough to know that the restored files are the same as the backed up ones, and there is no need to copy new versions.
    Cheers, Ed.

    Indeed not unexpected, however it would be easy to fix this in the future by linking the restore into the existing baseline (given that it is a direct copy of it) as it writes the files.
    It is worth mentioning because if you have a smallish backup disk (I don't) then writing the second baseline may flush out a number of your older weekly backups that you would rather have retained. It will also eventually mean that you will always have those two baselines and therefore restrict the number of valid backups that you can keep.
    Cheers, Ed.

  • Time Machine does not complete backup to Time Capsule

    Within the past few days my iMac will not complete a backup to my Time Capsule.   The two other computers connected to the Time Capsule appear to be backing up but they size of the backup is smaller.   The Time Machine starts but then stops after 10 or so minutes.   Also, the size of the to backup is ver large, and I have not added that much to my files since the last complete backup.
    Here is what I tried:
    1. Deleting the com/apple/Timecapsule.plist file and restarting the Time Capsule.
    2. turning off WIFI and connecting to an ethernet cable
    3. Verifying the disk (when connected to with the ethernet cable)
    Nothing worked although Deleting the com/apple/Timecapsule.plist file and restarting the Time Capsule it got about 50% through before crapping out.
    Appreciate any ideas.
    Thanks

    What OS is the computer running? Expect issues with Yosemite.. it is just not that reliable.
    How much space does it require and how much is available on the TC?
    What speed is the backup doing? If it is super slow it can trip out.
    You did the right things, using ethernet and verifying the old backup.. But if you upgraded to Yosemite (upgraded??) then I strongly recommend you start a completely new backup.
    Did you load the widget so you can actually check the log info.. to find out why TM stopped??
    A1 here. http://pondini.org/TM/Troubleshooting.html
    It is hard to fix issues when you don't even know what the issue is.

  • HT3275 I received this message and I'm unsure how to fix it "Time Machine couldn't complete backup to Time Capsule the backup disk image"/Volumes/The Vision Board/Alex Parry.sparsebundle" is already in use

    I received this message and I'm unsure how to fix it "Time Machine couldn't complete backup to Time Capsule the backup disk image“/Volumes/The Vision Board/Alex Parry.sparsebundle” is already in use

    Look at the more like this on the right column of the web page.
    This is the most common error here.. we answer it 5-10times every day.
    Simple method.. pull out the TC power cord .. count to 10.. plug in the TC power cord.
    Look at the other references for more info.

  • I recently upgraded to Mavericks and the time machine is failing to backup.  Time Machine began only backing up twice a day and now has stopped.

    I recently upgraded to Mavericks and the time machine is failing to backup.  Time Machine began only backing up twice a day and now has stopped.

    This is the error message I got:
    2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Error: (22) setxattr for key:com.apple.backupd.HostUUID path:/Volumes/TOSHIBA EXT/Backups.backupdb/Quincy’s iMac size:37
    2014-03-18 17:02:30 -0400 com.apple.backupd[4971]: Backup failed with error 2: 2

  • Time Machine randomly performing full backups instead of incremental

    I've been using a Time Capsule since October 2009 with my 13" MBP running Snow Leopard with no issues.
    A few weeks ago, I noticed Time Machine decided to do a full 160GB backup, which then filled the Time Capsule and then deleted older backups. It then kept trying to do full backups every single time, resulting in the error 'Not enough space'.
    I archived the backups from the Time Capsule, disabled Time Machine and completely erased the Time Capsule.
    I set up Time Machine again and it's been working for about a week, but it's doing the same thing again - trying to do another large HD sized backup of 160GB or so (the amount of data my drive has).
    I have noticed in the logs the following line
    *17/02/2010 13:36:16 com.apple.backupd[946] Event store UUIDs don't match for volume: HD*
    Which seems to appear as Time Machine starts to do it's full backup.
    Any ideas? It's getting to the point that Time Machine is becoming unusable as I can't rely on it.

    Cool, I'll give that a try.
    Log files are here. I did rename my machine to remove spaces and punctuation but haven't backed up since then (only a few hours ago).
    Should I resume this backup or erase the TC and start again? (I've also renamed the TC network and drive)
    Feb 20 00:16:14 marty com.apple.backupd[8919]: Starting standard backup
    Feb 20 00:16:14 marty com.apple.backupd[8919]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:16:22 marty com.apple.backupd[8919]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:16:32 marty com.apple.backupd[8919]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:16:32 marty com.apple.backupd[8919]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:16:38 marty com.apple.backupd[8919]: No pre-backup thinning needed: 1.13 GB requested (including padding), 264.22 GB available
    Feb 20 00:16:47 marty com.apple.backupd[8919]: Copied 8 files (15 KB) from volume HD.
    Feb 20 00:16:47 marty com.apple.backupd[8919]: Starting post-backup thinning
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-234422: 264.22 GB now available
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Deleted backup /Volumes/Time Machine Backups/Backups.backupdb/Marty/2010-02-18-225109: 264.22 GB now available
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Post-back up thinning complete: 2 expired backups removed
    Feb 20 00:16:48 marty com.apple.backupd[8919]: Backup completed successfully.
    Feb 20 00:16:50 marty com.apple.backupd[8919]: Ejected Time Machine disk image.
    Feb 20 00:16:51 marty com.apple.backupd[8919]: Ejected Time Machine network volume.
    Feb 20 00:23:42 marty com.apple.backupd[9017]: Starting standard backup
    Feb 20 00:23:42 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:23:52 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:24:11 marty com.apple.backupd[9017]: Backup canceled.
    Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
    Feb 20 00:24:14 marty com.apple.backupd[9017]: Ejected Time Machine network volume.
    Feb 20 00:25:24 marty com.apple.backupd[9017]: Starting standard backup
    Feb 20 00:25:24 marty com.apple.backupd[9017]: Attempting to mount network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:25:25 marty com.apple.backupd[9017]: Mounted network destination using URL: afp://[email protected]/Time%20Machine
    Feb 20 00:25:30 marty com.apple.backupd[9017]: Disk image /Volumes/Time Machine/Jordan’s MacBook Pro.sparsebundle mounted at: /Volumes/Time Machine Backups
    Feb 20 00:25:32 marty com.apple.backupd[9017]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    Feb 20 00:34:44 marty com.apple.backupd[9017]: No pre-backup thinning needed: 200.38 GB requested (including padding), 264.22 GB available
    Feb 20 00:35:46 marty com.apple.backupd[9017]: Copied 283 files (6.5 MB) from volume HD.
    Feb 20 00:35:46 marty com.apple.backupd[9017]: Backup canceled.
    Feb 20 00:35:49 marty com.apple.backupd[9017]: Ejected Time Machine disk image.
    Feb 20 00:35:50 marty com.apple.backupd[9017]: Ejected Time Machine network volume.

  • Full Backups Every Time?

    My time machine setup is doing full backups every hour! I've excluded a ton of folders I don't want, such as Fusion Virtual Machines, but it's still backing my Users folder in full every time. All 20gb...
    Anybody else seen this? I saw some other posts about checking the Console for particular errors during the backup, but I don't get any errors whatsoever.
    thanks in advance!

    Greetings,
    Time Machine will only back up what has changed, each hour, after the completion of the first full backup. If nothing has changed you'll see no change for that hour.
    I use a Firewire 400 drive and my first full backup took 1 hr and 40 minutes, or right at 42 Gig an hour - I don't use USB drives any more than I have to. I always use the GUID partition scheme and Mac OS Extended (Journaled).
    The subsequent backups take from a second or two to a few minutes, depending on the changes to the drives/partitions that I back up since that initial Time Machine backup.
    Check your consumed space by going to each drive icon on your desktop and do a "Get Info" and note the drive space used and what's left.
    I use TM on four different machines, each with their own Firewire drive and they all work as advertised.
    Good Luck my friend.
    Cheers,
    M.

  • Time Machine gives different full backup sizes

    After this recent Time Machine update I am no longer able to back up. When Time Machine computes the backup it tells me that it is 320GB, which is larger than my backup drive, so it can't back up. However, when I go into the Time Machine preferences it computes the estimated backup size as 272.52GB. Before this Time Machine update was applied my backups were happening with no issues.

    Mark Trolley wrote:
    Thank you. They must have changed the amount of extra space required with this latest patch
    It's been 20% since the early days of Leopard.
    because it was working fine up until that point.
    It may be a combination of things: the drive is clearly too small; while it varies widely depending on how you use your Mac, our general "rule of thumb" is that TM needs at least twice the space of the data it's backing-up.
    If you're like most of us, the amount of data on your system has been growing.
    And apparently Time Machine is doing a full backup, so it just got beyond the capacity of the disk to hold it all.
    Looks like I need a larger Time Machine disk.
    Yup. The good thing is, they continue to get less and less expensive.

  • Time machine does not recognize backups

    I need to do a restore because after a logic board replacement my apps are not showing as registered, in other words they are all asking for serial numbers. I would like to see if I can use time machine to restore these apps. I don't want to do a full restore using the OS X install CD because it says it erases the contents of the volume. I'm assuming that means teh system and apps will be restored but I'll lose my files.
    I can;t get time machine to recognize backups and I found this...
    Symptoms
    In the Mac OS X 10.5 Time Machine "time travel" window, past backups may not appear if your computer name includes certain characters.
    Products Affected
    Resolution
    Check your computer name in Sharing preferences. Make sure the computer name only includes ASCII characters from following set and is not blank (no matter which Mac OS X language version you are using):
    0123456789abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ
    so I changed my computer name accordingly but the backup folder in Backups.backupdb still has the old name with a character not allowed. Nothing I do to change priveleges allows me to rename the folder!
    Advice needed! Thanks!

    It is not a simple matter of the computer name. A simple rename of the backup doesn't do it. It my be necessary but its not the obstacle.
    The MAC address of the old board is in the Extended Attributes (EAs -"invisible" metadata) for the old board backups and the MAC address of the new board is in its EAs. If they MAC address in the EA doesn't match the MAC address of the machine that Time Machine is trying to backup it won't do it and it will start a new backup. That certainly appears to be the situation you face.
    You can see this by a simple check in terminal. Below is a sample I have two machines name Juvenal and Pliny. The xattr command with the -l option lists all the extended attributes of a file. For the backups of my systems it returns a value that is, in fact, the MAC address of that machine. If the MAC address of the target and source don't match Time Machine won't do the backup and will start a newbackup'
    ~ $xattr -l /Volumes/Backup\ of\ Juvenal/Backups.backupdb/Juvenal
    com.apple.backupd.BackupMachineAddress:
    0000 30 30 3A 31 64 3A 34 66 3A 34 61 3A 66 31 3A 64 00:1d:4f:1a:f4:d6
    0010 36 00
    ~ $xattr -l /Volumes/Backup\ of\ Pliny/Backups.backupdb/Pliny
    com.apple.backupd.BackupMachineAddress:
    0000 30 30 3A 31 62 3A 36 33 3A 33 66 3A 66 64 3A 37 00:1b:63:3f:fd:76
    0010 36 00
    The actual path to your backups will depend on your configuration and whether or not the backup is on a locally attached drive or not. Mine - in the example above - are on a TC and the results occur after opening the sparse bundles.
    The solution I pointed you do is trying to deal with this and change it so the MAC addresses match.
    I agree this is a known problem and warrant an official fix which should not be complicated.

  • USB thumb drive does full backup every time its plugged in

    4GB Corsair USB thumb drive.
    1 Partition, MBR, HFS+
    I have 2 computers. PowerMac G5 and Macbook Pro. Each have there own Time Machine drives. Each time I plug my USB drive into one of these computers, syslog has this:
    backupd[7080]: Starting standard backup
    backupd[7080]: Backing up to: /Volumes/Time Machine/Backups.backupdb
    backupd[7080]: Event store UUIDs don't match for volume: CORSAIR
    backupd[7080]: Node requires deep traversal:/Volumes/CORSAIR reason:kFSEDBEventFlagMustScanSubDirs|
    backupd[7080]: No pre-backup thinning needed: 1.22 GB requested (including padding), 6.31 GB available
    backupd[7080]: Copied 4181 files (507.4 MB) from volume CORSAIR.
    backupd[7080]: Copied 4556 files (507.5 MB) from volume Macintosh HD.
    backupd[7080]: No pre-backup thinning needed: 660.7 MB requested (including padding), 5.78 GB available
    backupd[7080]: Copied 9 files (0 bytes) from volume CORSAIR.
    backupd[7080]: Copied 536 files (205 KB) from volume Macintosh HD.
    backupd[7080]: Starting post-backup thinning
    backupd[7080]: Deleted backup /Volumes/Time Machine/Backups.backupdb/bartleby/2008-05-01-100926: 5.78 GB now available
    backupd[7080]: Post-back up thinning complete: 1 expired backups removed
    backupd[7080]: Backup completed successfully.
    Now, if I go plug the USB drive into the other computer, the same thing happens, and this cycle repeats over and over again. I tried re-formating the drive, deleting the backups from both Time Machine drives and starting from scratch. No luck.
    Thing is, I have a smaller 1GB usb thumb drive and it doesn't exhibit this behavior. I could go back and forth between computers and there is no UUID match problem. I guess for now I can exclude the USB drive from one of the computers and only have the backup on one Time Machine drive, but that is not optimal.
    The only difference between the two USB drives is the partition scheme. On the 1GB, it is using Apple Partition Map and 4GB is using MBR. The reason why I am using MBR is because with MBR the 4GB drives formats to 3.75GB, with APM 3.62GB and with GUID (intel macs) 3.42GB. So MBR gives me the maximum space.

    For a PPC mac the partition map for a Time Machine drive must be APM. For an Intel mac it must be GUID. In fact both kinds of mac are being successfully backed up to the same drive by some posters, but I doubt you'll get much luck with a partition map that isn't one of those.

  • Time Machine doing HUGE hourly backups

    TM seems to be doing gigantic backups every hour -- copying 2-4 GB worth of data each time. Now clearly I'm not modifying that much data on an hourly basis. Is there any way I can monitor which files are being copied?
    My naive expectation is that in TM Preferences, under the progress bar, there would be a little disclosure triangle that, when clicked, tells you the name of the file currently being copied. Of course no such thing exists. Is there any way of knowing what the heck is going on?

    Time Machine will back up data if anything has changed. Even the slightest change to permissions will force a new backup. For example: I defragged my hard drive recently. Since I optimized the metadata table and moved the files around, TM thought I had new versions and prompted doubled my sparsebundle size overnight. It did not bother to compare filenames or sizes (and I do not think iDefrag changes the "modified" date), but some some puny little flag somewhere had been changed so it backed the file up again. I really do like TM, but the more I use it, the more I can see that it really is not "smart" with respect to incremental backups.
    Anyway, that might be something for you to investigate. I'm willing to bet tat even if you change the name of a directory then change it right back, TM will backup it up fresh. Time Machine has a ways to go yet. Hopefully Apple will release a "2.0" version in the near future that will address many of the irregularities that seem to plague the program.

  • Time Machine Freezes during full backup

    I just got a new MacBook Pro. I am trying to create an initial Time Machine full backup.
    The process freezes after processing 6.39GB out of 462.76GB. Further, Time Machine
    also globally freezes after the following steps:
    Reboot
    Try full backup
    -- it freezes
    Stop backup
    -- backup stops
    Try to start backup again
    TimeMachine is now completely frozen. Further, all the top-right menus seem frozen.
    Try to restart machine
    Machine cannot completely shutdown -- it stays in a zombie state trying to shutdown forever
    Force shutdown (pressing power button continously until the machine shuts down).
    I've tried this process about 10 times.
    Same behavior using 4 different types of backup disks.
    (network attached via afs, direct usb, direct fire-wire).
    Here's the console output is below.
    The "freezing" seems to coincide with the output of:
    "kernel[0]: AppleVTD: waiting space (512)"
    Does anybody have any suggestions on how to fix this problem?
    Thanks!
    Luis.
    ====== Console output======
    10/23/12 12:14:48.677 AM com.apple.backupd[1052]: Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    10/23/12 12:14:48.700 AM com.apple.backupd[1052]: Ownership is disabled on the backup destination volume.  Enabling.
    10/23/12 12:14:49.283 AM com.apple.backupd[1052]: Forcing deep traversal on source: "Macintosh HD" (mount: '/' fsUUID: 6C558E68-8F4B-337F-8BB6-6721988887F1 eventDBUUID: 54A53EDD-B4AA-4C26-830B-37AE17F0CA69)
    10/23/12 12:14:53.278 AM coreservicesd[24]: Received request to reset fmod watch. Latest received id is 14820719323154. Latest sent id is 14820719323154
    10/23/12 12:14:53.463 AM com.apple.backupd[1052]: Backup content size: 440.85 GB excluded items size: 20.16 GB for volume Macintosh HD
    10/23/12 12:14:53.464 AM com.apple.backupd[1052]: Found 1095112 files (420.69 GB) needing backup
    10/23/12 12:14:53.465 AM com.apple.backupd[1052]: 504.83 GB required (including padding), 7.41 TB available
    10/23/12 12:14:53.471 AM com.apple.backupd[1052]: Waiting for index to be ready (100)
    10/23/12 12:15:31.916 AM mdworker[1136]: Unable to talk to lsboxd
    10/23/12 12:15:31.977 AM sandboxd[1137]: ([1136]) mdworker(1136) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:15:32.000 AM kernel[0]: Sandbox: sandboxd(1137) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:16:01.962 AM mdworker[1142]: Unable to talk to lsboxd
    10/23/12 12:16:02.019 AM sandboxd[1143]: ([1142]) mdworker(1142) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:16:02.000 AM kernel[0]: Sandbox: sandboxd(1143) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:17:03.350 AM mdworker[1153]: Unable to talk to lsboxd
    10/23/12 12:17:03.355 AM mdworker[1154]: Unable to talk to lsboxd
    10/23/12 12:17:03.433 AM sandboxd[1155]: ([1153]) mdworker(1153) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:17:03.441 AM sandboxd[1155]: ([1154]) mdworker(1154) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:17:03.000 AM kernel[0]: Sandbox: sandboxd(1155) deny mach-lookup com.apple.coresymbolicationd
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:17.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (512)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (463)
    10/23/12 12:18:18.000 AM kernel[0]: AppleVTD: waiting space (128)
    10/23/12 12:19:04.717 AM mdworker[1168]: Unable to talk to lsboxd
    10/23/12 12:19:04.721 AM mdworker[1167]: Unable to talk to lsboxd
    10/23/12 12:19:04.782 AM sandboxd[1169]: ([1168]) mdworker(1168) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:19:04.788 AM sandboxd[1169]: ([1167]) mdworker(1167) deny mach-lookup com.apple.ls.boxd
    10/23/12 12:19:04.000 AM kernel[0]: Sandbox: sandboxd(1169) deny mach-lookup com.apple.coresymbolicationd
    =====

    Please read this whole message before doing anything.
    This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.
    Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode* and log in to the account with the problem. The instructions provided by Apple are as follows:
    Shut down your computer, wait 30 seconds, and then hold down the shift key while pressing the power button.
    When you see the gray Apple logo, release the shift key.
    If you are prompted to log in, type your password, and then hold down the shift key again as you click Log in.
    Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.
    The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.
    *Note: If FileVault is enabled, or if a firmware password is set, or if the boot volume is a software RAID, you can’t boot in safe mode.
    Test while in safe mode. Same problem?
    After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

Maybe you are looking for