Time Machine running out of space but doesn't delete old backups

First some context:
I am running Parallels Desktop on a 2011 iMac. The VM is on a partition that is excluded from Time Machine.
I have a second partition where I copy the VM every night using CCC. (This avoids TM backing up a large VM every hour).
TM says initial backup is 220 GB. I have a 1TB USB drive attached. So normally, this works fine.
This morning 100GB were copied to my Parallels Desktop partition. So TM should copy something in excess of 100GB during backup.
Currently, only 15GB are free on my backup volume. But TM doesn't try to delete old backups. It doesn't seem to recognize the size of the backup. Instead when it starts, it predicts about 1GB to backup. Then during backup the amount grows (note that no new data is changed during backup!) and it finally hits the wall at 15GB because the disk is full.
Any idea why TM doesn't figure out the real backup size?
Here's the log from TM Buddy:
10.12.12 13:25:13,472 com.apple.backupd[27667]: Backing up to: /Volumes/Time Machine-Backups/Backups.backupdb
10.12.12 13:38:34,588 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk
10.12.12 13:38:34,000 kernel[0]: HFS: Low Disk: Vol: Time Machine-Backups freeblks: 38389, warninglimit: 38400
10.12.12 13:38:45,000 kernel[0]: HFS: Vol: Time Machine-Backups Very Low Disk: freeblks: 25589, dangerlimit: 25600
10.12.12 13:38:45,066 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk, very low disk
10.12.12 13:38:45,088 mds[42]: (Warning) Volume: Indexing reset and suspended on backup volume "/Volumes/Time Machine-Backups" because it is low on disk space.
10.12.12 13:39:47,794 KernelEventAgent[48]: tid 00000000 type 'hfs', mounted on '/Volumes/Time Machine-Backups', from '/dev/disk1s2', low disk
10.12.12 13:39:53,885 com.apple.backupd[27667]: Error: (-34) SrcErr:NO Copying /Volumes/WBackup/Parallels/Smart iMac Windows 7.pvm/Smart iMac Windows 7-0.hdd/Smart iMac Windows 7-0.hdd.0.{a09d01ec-5596-4f65-b4cd-86aeff90082f}.hds to /Volumes/Time Machine-Backups/Backups.backupdb/Smart iMac/2012-12-10-072536.inProgress/3380F092-9336-408F-90EB-387FDE60A79D/WBackup/ Parallels/Smart iMac Windows 7.pvm/Smart iMac Windows 7-0.hdd

I would highly recommend the following resource to help you with this problem:
http://pondini.org/TM/Troubleshooting.html
Hope this helps

Similar Messages

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 Running out of Space

Previously Time Machine keept my backups for months. 2 Days ago I got the message that the disk was full. I erased it and started anew. Today I get the message again and have only a few backups.
My main disk, the one I'm backing up is 561 gigs and the Time Machine disk is 1 TB. What has caused the change in behavior?

That Pondini resource is incredibly cool, but I am apparently not tech saavy enough to follow it all. I continue to get a many warnings that Time Machine could not complete the back-up (because the back-up is too large for the back-up disk, and the Time Capsule appears full.) This after several years of working flawlessly and thinking it automatically made room for more recent back-ups by just deleting older ones.
Do either of you have a recommendation for a novice? I have already unselected the "warn me" in preferences, but it hasn't helped. I did download the "buddy widget" that Pontini recommended and some of the pertinent things seem to say : "No expired back-ups exist---deleting oldest back-ups to make room. Back-up failed with error: Not enough available disk space on the target volume."
I don't know that I have done anything different other than a larger external HD was plugged in for awhile (and I never did exclude that manually.)
Should I just erase Time Machine and try to start over? TIA.

Time machine running out of space quickly-Why?

I set up a client with a new iMac in Dec2012. This was a migration from an older iMac and the initial load was 650GB via TM Restore. He has a lot of pictures and documents but also chose to have me "back everything up." This was a 10.8 start
Went to the SW for 3 months. His prime activity was taking pictures, adding to iphoto library.
Now 4 months later his 1TB external drive (LaCie/TB) is nearing capacity and things will start being deleted soon. Now at 10.8.3
I cannot believe how 300GB of data were added in this time period. I am wondering if there was some temporary file that is burried in one of these backups.
How do I explore other than review each backup and do a get info to see which backup "spiked" the drive.
Thanks for any suggestions

Triple-click anywhere in the line below to select it:
tmutil compare | open -f -a TextEdit
Copy the selected text to the Clipboard (command-C).
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).
The command may take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear.
A TextEdit window will open with the output of the command. Each line that begins with a plus sign (“+”) represents a file that has been added to the source volume since the last snapshot was taken. These files have not been backed up yet.
Each line that begins with an exclamation point (“!”) represents a file that has changed on the source volume. These files have been backed up, but not in their present state.
Each line that begins with a minus sign (“-“) represents a file that has been removed from the source volume.
Files that you’ve excluded from backup, or that are excluded automatically, are ignored.
At the end of the output, you’ll get some lines like the following:
Added:
Removed:
Changed:
These lines show the total amount of data added, removed, or changed on the source(s) since the last snapshot.

My 8GB iPod touch is running out of space, but all I have is 177 songs with no apps, videos, or pictures.

My 8GB iPod touch is running out of space, but all I have is 177 songs with no apps, videos, or pictures.

Connect the iPod to your computer and look at the storage used by the various categories as shown in the colored bargarph in iTunes.
Come back with the results.
What is the Other on my iPhone and How to Remove It
An "other" larger than abount 1 1/2 GB usually indicates that the "other" includes corrupted files.
First try:
"First you go settings/general/usage/music/then left swipe over music and press delete and you would think it deletes your music but it doesn't instead it deletes your other but make sure your ipod is connected to a computer while doing this"
as recommended by:
How do I get rid of "other" storage: Apple Support Communities
Next, usually restoring from backup eliminated the corrupted files. However, sometimes restoring to factory settings/new iPod is required.
To restore from backup see:
iOS: How to back up
To restore to factory settings/new iPod see:
iTunes: Restoring iOS software

Ipad 2 - 30gb and running out of space, but i don't have that many movies - can anyone help

ipad 2 - 30gb and running out of space, but i don't have that many movies - can anyone help? How do i find a directory of files that I can manage (PC user)?
thanks!

You might have to do some experimenting from iTunes on your computer.
Several months back, I had a phantom 5G of video. I unchecked ALL video files and synced the iPad and the 5G was still there. I was able to delete the 5G and bring it back by repeatedly unchecking and checking the "Sync Movies" box.
A "Restore" solved my problem. Be forewarned that it's not quick:
Connect via cable to the computer that you use for sync. From iTunes, select the iPad/iPod and then select the Summary tab. Follow directions for Restore and be sure to say "yes" to the backup. You will be warned that all data (apps, music, movies, etc.) will be erased but, as the Restore finishes, you will be asked if you wish the contents of the backup to be copied to the iPad/iPod. Again, say "yes."

Im running out of space, how do I clear old content temp files

Im running out of space, how do I clear old content temp files old apps?
i have done the browser cache and cleared history.I am clearing items off the macbook pro but is there other areas i should clean
Thanks

Im running out of space, how do I clear old content temp files old apps?
I'm not sure exactly what you're asking. Temp files get automatically deleted when you restart. Old apps you can either uninstall (if it was originally installed with an installer, there should be an uninstaller somewhere) or drag it to the trash. What's "old content"?
i have done the browser cache and cleared history.
This is not going to give you back much space.

Time Machine claims not enough space, but there's plenty

Hello --
I'm having a problem with my Time Machine backup ever since upgrading to Yosemite. After the initial backup, I get these errors: "The backup disk needs 838.03 GB for the backup but only 712.05 GB are available. Select a larger backup disk or make the backup smaller by excluding files."
However, there is plenty of space. The initial backup took up about 898 GB of my 1.61 TB machine. Subsequent incremental backups should only take up a fraction — and I'm confident that I haven't added hundreds of gigabytes of new data to my disk. However, each time Time Machine tries to run its backup, I get the same error.
Time Machine is backing up both my small internal hard drive (128 GB) and the rest of the backup comes from an external drive. It worked fine under Mavericks, but under Yosemite it seems that Time Machine doesn't realize that the hundreds of gigabytes on the external drive has already been backed up before and doesn't all need to be backed up again.
Any thoughts? I had a backup that was several months old earlier; once I started getting this error, I wiped that backup thinking that a fresh backup might sole the error. No such luck.
I'm running Yosemite 10.10.0 on a mid-2011 MacBook Air, backing up to a Sinology NAS. (My wife who is still using Mavericks is continuing to successfully backup to the same drive.)
Thanks everyone!
- geoff

I have the exact same problem with almost the same setup: MacBook Pro (Retina, 13-inch, Late 2012) running Yosemite 10.10, an external harddrive and a Time Capsule 2 TB (4th Generation, Version 7.6.4). I even took the same actions as geoff2 (deleting the complete set of backups from Mavericks and making a new complete backup on Yosemite). On my internal harddrive 270 GB are occupied, on my external harddrive around 980 GB are occupied and the MacBook of my girlfriend is also backed up to the Time Capsule. At the moment around 646 GB are available on the Time Capsule.
Now I get the same error message saying, that 977 GB are needed for a backup but only 650 GB are available. Interestingly backups without the external drive connected will complete without any problems.
The external drive has a "GUID Partition Table". So it seems both of Linc Davis suggestions don't apply to the problem (we both have either GUID Partition Table or Logical Volume Group and the issue appears both on a NAS-Storage and on a Time Capsule).
Looking for additional information I looked into the console and found the following report: "Inheritance scan may be required for '/Volumes/Dolphin', associated with previous UUID: BA36E38E-71F9-39E1-BF72-36AF9D4BB45F". "Dolphin" is the name of the external drive. What does that mean? Is it of any relevance? For more information I will post all the reports concerning the backup below (it's mainly about trying to free more space on the TC by deleting old backups). "Yosemite" is my internal OS X Volume, "Hamster" is the name of the Volume on the TC, "Nifty" is a Nifty mini drive in the SD-Card-Slot.
I already verified the backups using the Option-Click on the menu bar symbol and I deleted and rebuilt the Spotlight index but it changed nothing. We could of course delete the backup volume (NAS or TC) and start a new backup, but I have a feeling, that the issue will appear again afterwards. Any other suggestions?
08.11.14 16:46:06,033 com.apple.backupd[4227]: Starting manual backup
08.11.14 16:46:06,071 com.apple.backupd[4227]: Network destination already mounted at: /Volumes/Hamster
08.11.14 16:46:11,000 kernel[0]: hfs: mounted Time Machine-Backups on device disk6s2
08.11.14 16:46:13,146 com.apple.backupd[4227]: Disk image /Volumes/Hamster/Nikos MacBook Pro 13" (2).sparsebundle mounted at: /Volumes/Time Machine-Backups
08.11.14 16:46:14,908 com.apple.backupd[4227]: Backing up to /dev/disk6s2: /Volumes/Time Machine-Backups/Backups.backupdb
08.11.14 16:46:19,914 com.apple.backupd[4227]: Inheritance scan may be required for '/Volumes/Dolphin', associated with previous UUID: BA36E38E-71F9-39E1-BF72-36AF9D4BB45F
08.11.14 16:46:27,375 com.apple.backupd[4227]: Will copy (10 MB) from Yosemite
08.11.14 16:46:32,745 com.apple.backupd[4227]: Will copy (0 KB) from Dolphin
08.11.14 16:46:32,748 com.apple.backupd[4227]: Will copy (0 KB) from Nifty
08.11.14 16:46:32,749 com.apple.backupd[4227]: Found 137158 files (954.27 GB) needing backup
08.11.14 16:46:32,752 com.apple.backupd[4227]: 977.06 GB required (including padding), 646.65 GB available
08.11.14 16:46:32,765 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-08-164619.inProgress/B65EE357-083D-4E0B-900B-42910289B9C4 containing 4 KB; 646.65 GB now available, 977.06 GB required
08.11.14 16:46:32,767 com.apple.backupd[4227]: Removed 1 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:49:20,472 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-07-111400 containing 627.9 MB; 647.28 GB now available, 977.06 GB required
08.11.14 16:49:20,472 com.apple.backupd[4227]: Removed 2 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:50:12,817 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-07-171215 containing 59.4 MB; 647.34 GB now available, 977.06 GB required
08.11.14 16:50:12,818 com.apple.backupd[4227]: Removed 3 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:50:48,156 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-07-183323 containing 42.4 MB; 647.38 GB now available, 977.06 GB required
08.11.14 16:50:48,156 com.apple.backupd[4227]: Removed 4 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:51:07,147 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-08-112446 containing 25.3 MB; 647.41 GB now available, 977.06 GB required
08.11.14 16:51:07,147 com.apple.backupd[4227]: Removed 5 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:51:28,134 com.apple.backupd[4227]: Deleted backup /Volumes/Time Machine-Backups/Backups.backupdb/Nikos MacBook Pro 13" (2)/2014-11-08-132002 containing 11.5 MB; 647.42 GB now available, 977.06 GB required
08.11.14 16:51:28,134 com.apple.backupd[4227]: Removed 6 expired backups so far, more space is needed - deleting oldest backups to make room
08.11.14 16:51:28,135 com.apple.backupd[4227]: Deleted 6 backups containing 766.6 MB total; 647.42 GB now available, 977.06 GB required
08.11.14 16:51:28,136 com.apple.backupd[4227]: Backup date range was shortened: oldest backup is now Nov 8, 2014
08.11.14 16:51:29,353 com.apple.backupd[4227]: Backup failed with error 7: Not enough available disk space on the target volume.
08.11.14 16:51:36,000 kernel[0]: hfs: unmount initiated on Time Machine-Backups on device disk6s2
08.11.14 16:51:37,508 com.apple.backupd[4227]: Ejected Time Machine disk image: /Volumes/Hamster/Nikos MacBook Pro 13" (2).sparsebundle
08.11.14 16:51:38,227 com.apple.backupd[4227]: Ejected Time Machine network volume.
08.11.14 16:53:43,804 SystemUIServer[431]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc
08.11.14 16:53:43,806 com.apple.prefs.backup.remoteservice[529]: Attempt to use XPC with a MachService that has HideUntilCheckIn set. This will result in unpredictable behavior: com.apple.backupd.status.xpc

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.

Time Machine Disk out of space

Every time Time machine does a backup I get a message saying that the disk is full and it will delete the oldest backup. In fact, the disk has tons of free space. When I do Get Info on the disk it says that 214 gigabytes are available. My internal hard drive which it is backing up only has 22 gigabytes on it.
As things stand now I can only store about 6 days of backups and things will certainly get worse.
I am running Mac OS X 10.7.2. I have VMWare Fusion installed and Windows 7 as a virtual machine under Fusion.

here it is:
Filesystem                          Size   Used Avail Capacity Mounted on
/dev/disk0s2                       698Gi   46Gi 651Gi     7%    /
localhost:/x4-2qwsQFDj-Rw5mjpzuUI 698Gi 698Gi    0Bi   100%    /Volumes/MobileBackups
/dev/disk1s3                       371Gi 342Gi   28Gi    93%    /Volumes/Time Machine Disk
unknownb88d12299a84:~ sganarelle$
and here is the screenshot:

Time machine doesn't delete old backups when disk is full

TM disk is 750GB. It tells me there is not enough room for backup…then I look into TM and find there ARE NO BACKUPS anymore. (There were a few days ago.) All backups are gone, except for one two days ago, which was when I began getting the "no room" error.
I assume I've lost everything, as the TM disk shows only the backup from 2 days ago. True?
Do I just format and start again?
Is there a fix for this "no room" message? (It says oldest backups are deleted when disk becomes full. But it doesn't do it.)
Do people rely on this?

How much data is TM backing-up? (What's shown for +Estimated size of full backup+ under the exclusions box in TM Preferences > Options?)
Note that your Time Machine disk should, in most cases, be at least twice the size of the data it's backing-up. See #1 in the Frequently Asked Questions *User Tip,* also at the top of this forum.
It appears that Time Machine needed to do a large backup, perhaps a full one, for some reason, and deleted as many old backups as it could (but it won't ever delete the last remaining one, as that would leave you with no backup at all), trying to make room.
If in doubt, Click here to 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. Navigate to the backup in question, then copy and post all the messages for that run here, along with the amount of data that TM is backing-up.

Time Machine doesn't delete old backups

Hi,
I keep getting errors from the TM backup that the disk for backup is full. It appears that TM doesn't delete the old backups that are on the disk. Any idea why it is not deleting the backups to make space? I also checked the button to notify me when deleting....useless....I am using Lion/Mountain Lion
Thanks

When you have issues of this sort.. Pondini is your man..
See http://pondini.org/TM/Troubleshooting.html
There is no need for admin / Root / SU login to TM.. that will not achieve anything.
You can delete the current set of TM preferences and start over.. See A4.
You have to delete the whole existing backup to start over. Or archive it off as I said if you want historical record, and erase the disk.
You erase the TC by using Airport Utility, under disk is erase option.. that is the fastest way. A quick erase via AU takes about 1min. Do use any other erase option, as they will take several hours.
You can also delete a sparsebundle.. but it is a long and time consuming process. That is important though if you have multiple backups on the TC you do not wish to lose.
See Q12 here http://pondini.org/TM/FAQ.html
There are many many posts about how to speed up deletion of large backups.
eg https://discussions.apple.com/thread/2224110?tstart=0

HT201250 so what to do when its full and doesn't delete old backups? How can I manually get rid of 2010 backups?

My time machine is full and its SO VERY VERY VERY SLOW SLOW to do anything on it. I want to completelly kill backups from 2010 and 2011. How can I do this? I'd be ok killing all my backups and doing a fresh start.

Another thought: if you are prepared to delete all your backups (as you say), you could experiment by deleting a few early backups, then testing that Time Machine continues to allow restorations of some test file, and will continue to do automatic backups as usual. If so, delete as many old backups as you want. If TM does not continue to behave after the old backups have been deleted, erase the TM disc and start again.

Firefox 20 just installed. Crashes regularly on machine running Win7 Home Premium, but doesn't on my Vista PC

I have recently installed Firefox 20 on both my computers. One is a Dell mahine running Vista Home Premium, one is an Asus running Win 7 Home Premium. I have never had any trouble running Firefox on either of these machines before.
The computers are both synced and share bookmarks and all other syncable information
The Firefox on my Vista machine is stable, but the Win 7 machine crashes regularly, sometimes after just a few minutes of uptime regardless of what sites I visit or what I do with my browser.
Extensions: Adblock Plus 2.2.3, Avast Webrep 8.0.4103, British English Dictionary 1.19.1, DivX Plus Web Player HTML5 <video> 2.1.2.145, DownloadHelper 1.9.14, Forecastfox 2.2.2, Image Zoom 0.4.6, Microsot .NET framework assistant 1.3.1, Troubleshooter 1.1.a
Also lists Zonealarm Secrurity Engine 1.5.393.22 but this extension is described as incompatible with the browser.
Plugins: Avrobat 11.0.2.0, DivX Player 2.2.0.52, Divx Helper 1.1.0.6, Google Update 1.3.21.135, Itunes Detector 1.0.1.1, Java Development Toolkit 7,0.170.2 10.17.2.2., Nero Kwikmedia Helper 11.2.0, Nero 3D Vision 7.17.13.1422, Picasa 3.0.0.0, Quicktime Plugin 7.7.3 7.7.3.0, ReadDownloader 1.3.0.208, Realdownloader Chrome Background 1.3.0.208, Real HTML5 and Pepperflash same versions, Realplayer Download Plugin 16.0.0.282, Realplayer Gw Liveconnect 32bit 16.0.0.282, Shockwave Flash 11.6.602.180, SIlverlight 5.1.20125.0,
NpFFApi 1.0.0.1 (disabled)
VIsta PC is 32bit OS, Win7 PC is 64bit OS
Specs of Win7PC - Asus M281394, AMD Dual Core 3800+ chip, 4GB DDR2-800 RAM, Gforce GT 610 graphics, onboard sound, 2 hard drives (320GB and 500GB)
Graphics drivers and Windows updates all up to date on both computers

Hello davonuk, your Crash Report related with Trusteer Rapport, see:
[https://bugzilla.mozilla.org/show_bug.cgi?id=786153 Bug 786153]
(please don't comment in bug reports: https://bugzilla.mozilla.org/page.cgi?id=etiquette.html )
thank you

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!

Time Machine running out of space but doesn't delete old backups

Similar Messages

Maybe you are looking for