The backup volume ran out of space unexpectedly!?!?

I have been backing up all my data to a 100GB HD for 9 months with absolutely no problem, until today it popped up and say
"The backup volume ran out of space unexpectedly. Time Machine will try to make more space available by removing expired backups during the next scheduled backup."
I still have 2.6 GB space available and the backup went on as usual, except after "preparing", the xxMB out of xxMB change together. I rebooted my macbook and same thing happened again.
Is there anything I can do? I thought TM would delete my old back ups in order to make some space for my latest ones.
Many thanks!

Yes, usually it does. The "unexpected" part is not usual.
First, is there other data on the TM disk? If so, is it in the same partition?
Second, it sounds like TM may be trying to do a full backup (everything on your system). Have you had any of the following: Hardware repairs (if so, what?); done a full restore; gone more than a few days without a successful backup?
Third, how old is your oldest backup?
And there may be better messages in your logs. Download the +Time Machine Buddy+ widget. It shows the messages from your logs for one TM backup run at a time, in a small window. If you see something there that seems suspicious, copy and post the messages here (be sure to get them all, as sometimes they overflow the small window).

Similar Messages

  • Time Machine:The backup disk ran out of space unexpectedly. .....

    Hi,
    I upgraded to Mountain Lion when it was released and yesterday I began getting this notice from Time Machine:
    "The backup disk ran out of space unexpectedly. Time Machine will try to make more space available by removing expired backups during the next scheduled backup."
    I have a one terra external hard drive with exclusively Time Machine.  It says it has 3.4 gigabytes available, but isn't deleting old backups and making room for new, like before.  I tried the "encrypting" solution, but it still keeps on giving me this message.  Should I erase and format?  If so, what option should I chose to format?
    My Hard Drive has 240 gigabytes, so 1Tb should be more than enough.
    Thank you!
    Gloria

    SuperDuper and Time Machine are two completely different backup utilities. If you want something like what SuperDuper does then don't use Time Machine. You have many other options that won't use up all the space on your backup drive:
    Backup Software Recommendations
    Carbon Copy Cloner
    Data Backup
    Deja Vu
    SuperDuper!
    Synk Pro
    Tri-Backup
    Others may be found at VersionTracker or MacUpdate.
    Visit The XLab FAQs and read the FAQ on backup and restore.  Also read How to Back Up and Restore Your Files.
    Do the following to erase your drive:
    Erase a Drive
    1. Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.

  • Time Machine Error: The backup disk ran out of space unexpectedly.

    I keep getting the following message when I try to back up my MacBook using Time Machine: "The backup disk ran out of space unexpectedly. Time Machine will try to make more space available by removing expired backups during the next scheduled backup."
    However, I have deleted everything from the external harddrive, which holds 500 GB. I have only used 38.9 GB of space on my computer. The errors being recorded are as follows:
    Starting standard backup
    Backing up to: /Volumes/Iomega_HDD/Backups.backupdb
    Error parsing SystemMigration.log to determine source volume of system migration.
    Backup content size: 36.5 GB excluded items size: 5.0 GB for volume Macintosh HD
    No pre-backup thinning needed: 38.19 GB requested (including padding), 437.50 GB available
    Waiting for index to be ready (101)
    Stopping backup.
    Error: (-34) SrcErr:NO Copying /Applications/.DS_Store to /Volumes/Iomega_HDD/Backups.backupdb/Jennifer Kwapisz’s MacBook/2011-08-06-113458.inProgress/9273E0A6-8BD8-4282-ACEC-E1E410605A89/Macin tosh HD/Applications
    Copied 0 files (36 KB) from volume Macintosh HD.
    Copy stage failed with error:28
    Backup failed with error: 28
    Any idea what's going on and what I need to do to fix it?

    Please read this:
    http://pondini.org/TM/C18.html
    Ciao.

  • Time Machine problem: backup disk ran out of space unexpectedly

    Hi all,
    I'm having trouble with Time Machine.  Each time it tries to do a backup, it errors out.
    Here is the most recent log from TM Buddy:
    Starting manual backup
    Backing up to: /Volumes/Time Machine Backup/Backups.backupdb
    Using file event preflight for Macintosh HD
    Will copy (740.5 MB) from Macintosh HD
    Found 1702 files (741 MB) needing backup
    2.43 GB required (including padding), 57.43 GB available
    Stopping backup.
    Error: (-34) SrcErr:NO Copying /Users/Alan/Pictures/iPhoto Library (original)/Masters/2013/02/25/20130225-174952/IMG_1601.MOV to /Volumes/Time Machine Backup/Backups.backupdb/Alan’s iMac/2013-07-27-024450.inProgress/FE0FAB85-8482-43AF-B2D2-CB4804D0B0E9/Macintos h HD/Users/Alan/Pictures/iPhoto Library (original)/Masters/2013/02/25/20130225-174952
    Copied 111323 files (57.29 GB) from volume Macintosh HD.
    Copy stage failed with error:28
    Backup failed with error: 28
    It usually errors out in the middle of trying to backup the very large "iPhoto Library (original)" file, so I went digging into this file back in time.  About a month ago, I emptied the trash in iPhoto for the first time, and the size of the iPhoto Library file shrank from 87 GB down to just 1 GB.  That seems rather extreme, and according to iPhoto, I still should have approximately 62 GB of photos remaining.  The last completed backup that Time Machine was able to make had the library file at 800 MB.  Even more strange, the current iPhoto Library file on my iMac is 83 GB.  So I think this is the reason why TM is trying to make another complete backup of this file.
    I'm guessing that if TM is able to completely backup the iPhoto Library file, the errors will go away.  Does this seem like a reasonable hypothesis?
    If so, then I'll need to delete files on the TM volume to make more room.  At one point last year, I had tried splitting my monolithic iPhoto Library into 3 smaller libraries, and later merged them again under the current name "iPhoto Library (original)".  These changes/instances of the libraries were all captured on TM.  If I delete the original monolithic iPhoto Library file (named "iPhoto Library") on the TM volume, will I also lose my current iPhoto library (named "iPhoto Library (original)"?  In other words, how does TM distinguish one file from another?  By the file name?  Or some other more permanent identifier?

    The backup volume was full. That shouldn't happen, because TM is supposed to manage disk space by deleting snapshots as needed to make room for a new one, up to the last complete snapshot, which is never removed automatically. Normally, a snapshot won't be started if there isn't enough space for it.
    First, I strongly suggest that you make a new backup (not necessarily with Time Machine) on another external drive. A single backup isn't enough to be safe.
    One possibility is that you were writing other data to the volume during the backup. Apple recommends that no other data be stored on a backup volume.
    If you've moved any files to the Trash on the backup volume, empty the Trash.
    Sometimes a reboot will clear the error.
    Otherwise, turn Time Machine OFF temporarily in its preference pane. Launch Disk Utility, select the backup volume, and run Repair Disk. That operation may take a few hours. If the volume is repaired successfully, or if no problems are found, try another backup.
    If TM still isn't working right, boot into Recovery (command-R at startup) and repair the startup volume ("Macintosh HD," unless you gave it a different name.) Reboot as usual and try TM again.
    As a last resort, put the backup drive aside and don't use it until you're sure you'll no longer need the data. Then erase it and start over. Do this only if you have at least one other backup device.

  • Message: Backup disc ran out of space!

    Trying to do my first backup using Time Machine but keep as soon as backup starts, it stops and I get this message:
    "Time Machine could not complete backup - disc ran out of space" -- but I'm using new external drive connected via firewire.

    Is the new external drive larger than the contents of your hard drive? Is it formatted properly? (Mac OS Extended (Journaled))

  • Time Machine pops up a dialog window that the disk ran out of space unexpectedly.

    This happens hourly, it seems.  Should not be a problem if TM deletes the oldest backup (which it says it will do), so I don't care!  VERY ANNOYING.  How do I stop that message from popping up?
    OS 10.8.4
    TM drive is connected via USB.

    If you have more than one user account, these instructions must be carried out as an administrator.
    Launch the Console application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
    Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
    View ▹ Show Log List
    from the menu bar.
    Enter the word "Starting" (without the quotes) in the String Matching text field. You should now see log messages with the words "Starting * backup," where * represents any of the words "automatic," "manual," or "standard." Note the timestamp of the last such message. Clear the text field and scroll back in the log to that time. Select the messages timestamped from then until the end of the backup, or the end of the log if that's not clear. Copy them (command-C) to the Clipboard. Paste (command-V) into a reply to this message.
    If all you see are messages that contain the word "Starting," you didn't clear the search box.
    If there are runs of repeated messages, post only one example of each. Don't post many repetitions of the same message.
    When posting a log extract, be selective. Don't post more than is requested.
    Please do not indiscriminately dump thousands of lines from the log into this discussion.
    Some personal information, such as the names of your files, may be included — anonymize before posting.

  • Time Machine failure: Disk run out of space unexpectedly

    Hi
    I'm having serious problems in the last few days with Time Machine backups.
    I have an iMac '27 (late 2009) running Mountain Lion 10.8.2. The internal disk is 1 TB, and I use an external FW HD LaCie d2 Quadra 1 TB for my TM backups. After 3 years the disk is always full, but old backups were regularly removed. All the possible source of large variable files were excluded long time ago (VM disks, temporary directories, large download files).
    TM used to work quite smoothly, but now, since 10 days, the backup fails with the message
    "The backup disk ran out of space unexpectedly. Time Machine will try to make more space available by removing expired backups during the next scheduled backup."
    I've checked previous messages in the forum about such an error, but the various cases do not seem to match my specific problem (or I was not able to find the message with working answer).
    It seems that the "unexpected" problem is related to the fact that Time Machine is trying to backup again a large part of my filesystem, and it determines this fact only after the backup starts (so there is no pre-cleaning): when it happens I can see that the target size of the backup increases over time, while more and more data are written on the disk, until the disk is full.
    I'll try to summarize my situations with an itemized list:
    The current backup fails because it runs out of space, leaving an .inprogress file behind
    The latest backup did not fail: the log report a successful backup (checked with Time Machine Buddy)
    Examining the content of the latest backup, the one that did not fails, shows that some system directories, /Applications, /usr, and /bin are missing
    So, possibly, the "unexpected" error happens because the system is backing up a lot of stuff (like 60GB), and TM discover this only after it starts writing the files
    I've verified with Disk Utility both the TM disk and the internal HD, and they both report no problem.
    After some digging around, I was able to make TM work again removing the .inprogress file (using the Pondini instructions), removing (using the "Star Wars" interface) the latest backup, the one with the incomplete content, and removing a few older backups to create some more free space.
    The first time I thought it was a transient problem, but it happened again after a few days.
    So the real issue is, why the latest successful backup is actually incomplete, with a large number of directories missing, but there is no hint of this in the logs?
    I've read that old LaCie HDs might have problems with Mountain Lion, and with its power saving settings. May this be the cause? I did already turn off the power saving setting (put HD to sleep when possible) before the latest failure, but nothing changed.
    I've also tried to update the d2 Quadra firmware, as indicated by other messages and on LaCie website, but the update fails and the provided instructions are less than useful (I'll try to contact LaCie on this issue).
    My doubt is that this does not seem a power save issue... the failed backups happen while I'm actually using the machine (so no wake up/disk spin issue seems to happen), and the backups starts with no problem: they just finish abruptly with no apparent reason but with a success message.
    Does anyone have problems similar to mine (successful but incomplete TM snapshots)? Is the problem triggered by the HD firmware, or there are other possible causes?
    I plan to repair the TM one more time, and then keep it turned off to run only manual backups, but I'm aware that there is no guarantee that also a controlled manually started backup is not going to fail in a similar way.
    Thanks for any suggestion.
    Maurizio

    I am not running out of space, but I do have the same problem.  Every so often TM does a backup which is about 60 GB bigger than expected.   The  extra is always a new backup of /System /Applications /usr etc. - that is the 'system files'.
    The key thing is, as you have noticed:
    Examining the content of the latest backup, the one that did not fail, shows that some system directories, /Applications, /usr, and /bin are missing
    As a consequence the next backup is, in my case, 60 GB bigger because it includes all the system files.
    It is as if 'systemFilesExcluded' was turned on for the previous backup (the one that 'did not fail').  But I have looked in the .exclusions.plist for this backup and it is exactly the same as for other backups and does include:
            <key>systemFilesExcluded</key>
            <false/>
    It seems that TM is treating this as if <true/>.
    Like you, I have done a disk verify and it finds no errors.
    I think this must be a bug.  I have had this on four occassions since upgrading to Mountain Lion.  And it is doing a large one right now - I have caught it in the act!

  • I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

    I backup to an external hdd with Time Machine, when it ran out of space it did not delete old backups, now my internal hdd says its full when before it had heaps of space. I have searched for extra files but cant find any. Can anyone help, please.

    First, empty the Trash if you haven't already done so. Then reboot. That will temporarily free up some space.
    To locate large files, you can use Spotlight as described here. That method may not find large folders that contain a lot of small files.
    You can also use a tool such as OmniDiskSweeper (ODS) to explore your volume and find out what's taking up the space. You can delete files with it, but don't do that unless you're sure that you know what you're deleting and that all data is safely backed up. That means you have multiple backups, not just one.
    Proceed further only if the problem hasn't been solved.
    ODS can't see the whole filesystem when you run it just by double-clicking; it only sees files that you have permission to read. To see everything, you have to run it as root.
    Back up all data now.
    Install ODS in the Applications folder as usual.
    Triple-click the line of text below to select it, then copy the selected text to the Clipboard (command-C):sudo /Applications/OmniDiskSweeper.app/Contents/MacOS/OmniDiskSweeper
    Launch the Terminal application in any of the following ways:
    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
    ☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
    I don't recommend that you make a habit of doing this. Don't delete anything while running ODS as root. If something needs to be deleted, make sure you know what it is and how it got there, and then delete it by other, safer, means.
    When you're done with ODS, quit it and also quit Terminal.

  • Time Machine Unexpectedly Ran Out Of Space

    Hello everybody.  I am running Time Machine as my main form of backup for my system which consists of about 2 gigs of data stored on 3 internal drives on my mac pro. 
    A few months ago I started getting the message that my 3TB time machine drive "unexpectedly ran out of space".   I went into the drive and deleted the older backup files but this only seemed to solve the problem for a couple days and then the same issue would return.  I decided to get rid of that drive and buy a 4TB hard drive (which has plenty more space than the amount of data I am backing up). 
    To my surprise I continue to get the same message (even though now the drive is about double the size of the actual data I need backed up).  What can I do to set things up so my data is being backed up automatically and I don't have to go in and constantly delete the older backups?  I would rather not have all the incremental backups and just have a reliable automatic system in place.  
    Thanks for your time and input!!

    Try C18  in the 1st linked article.
    Time Machine Troubleshooting
    Time Machine Troubleshooting Problems

  • I ran out of space on my time machine  because I bought a new I MAC to replace the old one.  So I copied the old one on the new one  and in addition to that I own a macbook.  So what should I do erase the old IMAC on my  Time capsule ? Shall I reset it?

    I ran out of space on my time machine  because I bought a new I MAC to replace the old one.  So I copied the old one on the new one  and in addition to that I own a macbook.  So what should I do erase the old IMAC on my  Time capsule ? Shall I reset it?

    Go to the airport utility and erase the TC disk.. a quick erase is fine and takes less than 1min usually.
    A one pass erase takes several hours depending on how big the hard disk is.. but is somewhat safer in that it tests the drive condition. I normally don't bother for a TM backup.
    When you start over you should be able to fit both backups on the TC.. assuming the disk is 2x larger at least than the space used on both the MB and the iMac.
    If not you can also add a USB drive to the TC, and use that for one of the computers.
    The slowest one is best.. as USB is slow.. but fast enough for wireless you won't notice much.

  • (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink?

    (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

    (final cut pro x 10.0.9 )After numerous troubleshooting tips, I am still getting the dreadful your disk have ran out of space, your events have moved or permissions have changed. This happened after I moved some files to another drive. They won't relink eventhough the files are there.

  • The query processor ran out of stack space during query optimization. Please simplify the query

    Can you suggest me that what should i do in this case.
    Actually i am having one table that is a MasterTable.I am referring this table in more than 300 tables that means i am having foreign key of this primary key in 300+ tables.
    due to this i am getting following error during deleting any row,
    doesn't matter that data is existing in reference table or not.
    Error that i am getting is 
    "The query processor ran out of stack space during query optimization. Please simplify the query"
    Can you suggest me that what should i do to avoid this error,because i am unable to delete this entry.
    Apart from it,i am getting performance problem too,so is it due to such huge FK on it.
    Please suggest me on following points
    1. Is it worst way to handle it,if yes then please suggest me solution for it.
    2. If it is a correct way then what should i do if getting error during deleting any record.
    3. Is it right to create Foreign key on each table where i am saving data of this master. if no then how to manage integrity.
    4. What people do in huge database when they wants to create foreign key for any primary key.
    5. Can you suggest me that how DBA's are handling this in big database,where they are having huge no. of tables.

    The most common reason of getting such error is having more than 253 foreign key constraints on a table. 
    The max limit is documented here:
    http://msdn.microsoft.com/en-us/library/ms143432(SQL.90).aspx 
    Although a table can contain an unlimited number of FOREIGN KEY constraints, the recommended maximum is 253. Depending on the hardware configuration hosting SQL Server, specifying additional foreign key constraints may be expensive for the query
    optimizer to process. If you are on 32 bit, then you might want to move to 64 bit to get little bigger stack space but eventually having 300 FK is not something which would work in long run.
    Balmukund Lakhani | Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
    This posting is provided "AS IS" with no warranties, and confers no rights.
    My Blog |
    Team Blog | @Twitter
    Author: SQL Server 2012 AlwaysOn -
    Paperback, Kindle

  • Time machine ran out of space

    I keep getting this error and I know it ran out of space. I have two 1 tb drives that are being used by time machine. But it seems like time machine is not making room for the next backup. I understand this is supposed to be automatic. But it's not working right. I am getting very annoyed by this error. I do not want to manually delete backups.

    Sep 16 20:08:50 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Backup failed with error: 28
    Sep 16 20:08:50 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Starting automatic backup
    Sep 16 20:08:50 8-core-12-GB-MacPro-221.local com.apple.SecurityServer[30]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [26] for authorization created by '/usr/libexec/UserEventAgent' [26] (100012,0)
    Sep 16 20:08:50 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Backing up to: /Volumes/Terra 2/Backups.backupdb
    Sep 16 20:08:54 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Using file event preflight for Macintosh HD
    Sep 16 20:08:59 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Will copy (4.5 MB) from Macintosh HD
    Sep 16 20:08:59 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Using file event preflight for terra
    Sep 16 20:09:01 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Will copy (105.8 MB) from terra
    Sep 16 20:09:01 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Found 1383 files (110.3 MB) needing backup
    Sep 16 20:09:01 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: 1.3 GB required (including padding), 56.79 GB available
    Sep 16 20:09:57 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Copied 6203 files (4.5 MB) from volume Macintosh HD.
    Sep 16 20:10:23 8-core-12-GB-MacPro-221.local SyncServer[57174]: [0x7f953940be60] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.
    Sep 16 20:10:36 8-core-12-GB-MacPro-221.local iTunes[47734]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:10:36 8-core-12-GB-MacPro-221.local ath[55623]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:12:45 8-core-12-GB-MacPro-221.local com.apple.usbmuxd[45757]: HandleUSBMuxConnect Client 0x103a09bc0-AppleMobileDeviceHelper/com.apple.SyncServices.AppleMobileDeviceHel per requesting attach to 0x67:62078 failed, no such device
    Sep 16 20:12:45 8-core-12-GB-MacPro-221.local AppleMobileDeviceHelper[47743]: AMDeviceConnect (thread 0x7fff77667180): Could not connect to lockdown port (62078) on device 103 - 957ae2af8b313741fb4a856f9cba8d5f24589a0f: 0xe8000084.
    Sep 16 20:12:45 8-core-12-GB-MacPro-221.local AppleMobileDeviceHelper[47743]: 47743:2003202432|DeviceLinkListener.c:_copyMobileDeviceValue| ERROR: Could not connect to attached device: This device is no longer connected. (132)
    Sep 16 20:12:45 8-core-12-GB-MacPro-221.local SyncServer[57187]: [0x7f9d18c0be60] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.
    Sep 16 20:12:55 8-core-12-GB-MacPro-221.local iTunes[47734]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:12:55 8-core-12-GB-MacPro-221.local ath[55623]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:15:31 8-core-12-GB-MacPro-221.local SyncServer[57202]: [0x7fbec2c0be60] |DataManager|Warning| Client com.apple.Mail sync alert tool path /System/Library/Frameworks/Message.framework/Resources/MailSync does not exist.
    Sep 16 20:16:09 8-core-12-GB-MacPro-221.local iTunes[47734]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:16:09 8-core-12-GB-MacPro-221.local ath[55623]: _NotificationSocketReadCallbackGCD (thread 0x7fff77667180): Unexpected connection closure...
    Sep 16 20:17:22 8-core-12-GB-MacPro-221.local WindowServer[182]: CGXDisableUpdate: UI updates were forcibly disabled by application "Console" for over 1.00 seconds. Server has re-enabled them.
    Sep 16 20:17:22 8-core-12-GB-MacPro-221.local WindowServer[182]: reenable_update_for_connection: UI updates were finally reenabled by application "Console" after 1.11 seconds (server forcibly re-enabled them after 1.00 seconds)
    Sep 16 20:18:50 8-core-12-GB-MacPro-221 kernel[0]: CODE SIGNING: cs_invalid_page(0x1000): p=57233[GoogleSoftwareUp] clearing CS_VALID
    Sep 16 20:21:57 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 received event(s) VQ_LOWDISK (4)
    Sep 16 20:21:57 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 type 'hfs', mounted on '/Volumes/Terra 2', from '/dev/disk0s2', low disk
    Sep 16 20:21:57 8-core-12-GB-MacPro-221 kernel[0]: HFS: Low Disk: Vol: Terra 2 freeblks: 38342, warninglimit: 38400
    Sep 16 20:21:59 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 received event(s) VQ_LOWDISK, VQ_VERYLOWDISK (516)
    Sep 16 20:21:59 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 type 'hfs', mounted on '/Volumes/Terra 2', from '/dev/disk0s2', low disk, very low disk
    Sep 16 20:21:59 8-core-12-GB-MacPro-221 kernel[0]: HFS: Vol: Terra 2 Very Low Disk: freeblks: 25565, dangerlimit: 25600
    Sep 16 20:21:59 8-core-12-GB-MacPro-221.local mds[52]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/Terra 2" because it is low on disk space.
    Sep 16 20:22:14 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 received event(s) VQ_LOWDISK (4)
    Sep 16 20:22:14 8-core-12-GB-MacPro-221.local KernelEventAgent[58]: tid 00000000 type 'hfs', mounted on '/Volumes/Terra 2', from '/dev/disk0s2', low disk
    Sep 16 20:22:14 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Stopping backup.
    Sep 16 20:22:14 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Error: (-34) SrcErr:NO Copying /Volumes/terra/winserv2008/Windows 7.pvm/Windows 7-0.hdd/Windows 7-0.hdd.0.{5fbaabe3-6958-40ff-92a7-860e329aab41}.hds to /Volumes/Terra 2/Backups.backupdb/8 core 12 GB MacPro (158)/2012-09-15-230849.inProgress/DFFFF014-5A28-4864-97AC-0184CB7EB3A9/terra/w inserv2008/Windows 7.pvm/Windows 7-0.hdd
    Sep 16 20:22:14 8-core-12-GB-MacPro-221.local mds[52]: (/)(Warning) IndexQuery in bool preIterate_FSI(SISearchCtx_FSI *):Throttling inefficient file system query
    Sep 16 20:22:15 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Copied 14038 files (59.95 GB) from volume terra.
    Sep 16 20:22:15 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Copy stage failed with error:28
    Sep 16 20:22:26 8-core-12-GB-MacPro-221.local com.apple.SecurityServer[30]: Succeeded authorizing right 'com.apple.ServiceManagement.daemons.modify' by client '/usr/libexec/UserEventAgent' [26] for authorization created by '/usr/libexec/UserEventAgent' [26] (100012,0)
    Sep 16 20:22:26 8-core-12-GB-MacPro-221.local com.apple.backupd[55483]: Backup failed with error: 28
    Sep 16 20:23:22 8-core-12-GB-MacPro-221.local Google Chrome Helper[57259]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.
    Sep 16 20:23:22 8-core-12-GB-MacPro-221.local Google Chrome Helper[57258]: Unsure about the internals of CFAllocator but going to patch them anyway. If there is a crash inside of CFAllocatorAllocate, please report it at http://crbug.com/117476 . If there is a crash and it is NOT inside of CFAllocatorAllocate, it is NOT RELATED. DO NOT REPORT IT THERE but rather FILE A NEW BUG.

  • This backup is too large for the backup volume - ridiculous backup size

    I have had big problems with Time Machine today. I have been successfully using it for 2 months now. I have about 30Gb spare on my iMac hard drive (out of 233Gb) and my Time Machine uses 195Gb out of 466Gb available.
    However, today I have lost all my Time Machine history except for one backup made this morning, and I am now getting an error message saying:
    "Time Machine Error
    This backup is too large for the backup volume. The backup requires 161061280.0 GB but only 270.4 GB are available.
    To select a larger volume, or make backup smaller by excluding files, open System Preferences and choose Time Machine"
    Clearly the required backup volume is wrong - that's 161,000.0TB!!!
    The same message has come up 3 times now.
    Can anyone help/advise on what to do next?

    Thanks Peggy,
    I re-indexed Spotlight and ran Time Machine again, but got exactly the same error message and the same massive storage required.
    I've opened Console as you suggested and these are a set of the messages from one back-up attempt yesterday (Console doesn' show anything earlier than 17.32 yesterday - but the problem started earlier than that I believe):
    "16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backup requested by automatic scheduler
    16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Starting standard backup
    16/01/2008 17:32:52 /System/Library/CoreServices/backupd[326] Backing up to: /Volumes/Time Machine Backups/Backups.backupdb
    16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Event store UUIDs don't match for volume iMac Hard Drive
    16/01/2008 17:32:53 /System/Library/CoreServices/backupd[326] Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Starting pre-backup thinning: 157286.40 TB requested (including padding), 270.35 GB available
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] No expired backups exist - deleting oldest backups to make room
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Error: backup disk is full - all 0 possible backups were removed, but space is still needed.
    16/01/2008 17:44:48 /System/Library/CoreServices/backupd[326] Backup Failed: unable to free 157286.40 TB needed space
    16/01/2008 17:44:49 /System/Library/CoreServices/backupd[326] Backup failed with error: Not enough available disk space on the target volume."

  • This backup is too large for the backup volume - ridiculous Size!!!

    Hi .. i own a macbook 13" aluminium, I have Snow Leopard 10.6.2 , and i change my internal hard drive to a 500Gb.
    I bought 1Tb Western Digital My Book USB External Drive to use it for back ups using Time machine.. at the beginning worked great, when i changed my hard drive i restore everything in lest than 2 hours.
    Then one time, it said that the hard drive where going out of space, and i said to delete the oldest backups, it erase everything and kept the last back up. Since then, it came a message
    *_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
    its ridiculous, when i go to the time machine preference, it said that the full size back up it would take 83Gb only.
    I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
    Please anyone... i am desperate
    Thanks Again
    Daniel

    DanielFaour wrote:
    *_+This backup is too large for the backup volume. The backup requires 2.73EB but only 995 Gb are available.*+_
    Hi, and welcome to the forums.
    That message seems to indicate that something is corrupted on your internal HD. Do a +*Verify Disk+* on it, per #A5 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum.
    If that finds errors, you'll have to use the procedure in the yellow box there to Repair them.
    If that does not find errors, Restart your Mac and do a "full reset" of Time Machine, per #A4 there.
    I tried everything, formatting the unit, taking out the partition , and making it out again, it makes the first full back up, but then the same message...
    What partition? Are there multiple partitions on your TM drive? How large is the one for Time Machine? Check the setup per #C1 of the Troubleshooting Tip.

Maybe you are looking for

  • How do you create a PIP in a multicam clip?

    I know how to create a picture-in-pictre where I would overlay the PIP clip over the primary clip in my timeline, and reduce the size of the PIP window. But I would like to use PIP in a multicam clip. I usually fully switch from one angle to the othe

  • Need information about location of printer

    hello, I need to get all informations (like status, location, type and comment) about a selected printer. I used PrinterJob.lookupPrintServices() to read all available printer. how can i get all this information under windows xp ?

  • Data Dictionary auto-entry

    I've created a database table and table maintenance screen with SE11. The table contains User, Date and Time fields. I'd like these fields to be automatically filled when transaction SM30 is used to create table entries. Has anyone in the forum done

  • FLASHBACK TROJAN?

    any info about flash back trojan?

  • BPS/BCS/CPM  study material

    Hi Gurus, If possible any one please help me with some useful material on SEM-BPS/BCS/CPM etc., I am verymuch thankful to you if anybody help me on this. Thanks, MALLI NAIDU