Time Machine incorrectly reporting free space

I'm seeing this on Mavericks (retina MBP, 500GB SSD about 60% utilized) .
I've got a AFP network share that I copied a clean 800GB sparesebundle to. I use Disk Utility to mount and verify it, and it says, 650MB used, which means it's essentially 99% empty.
I unmount and attempt a backup with this disk. Almost immediately Time Machine reports that only 97GB free of the 800GB disk and can't continue because it needs ~275GB (a first time backup).
I unmount and remount it with Disk Utility and sure enough, it says it only has 97GB free. I re-run repair and the disk then reports 640MB used again. No matter what, Time Machine reports that only 98GB is free even immediately after I repair and even erase the Time Machine disk!
This is repeatable and reproducable.
The sparsebundle was created with:
hdiutil create -size 800g -type SPARSEBUNDLE -nospotlight -volname "Backup of My Mac" -fs "Case-sensitive Journaled HFS+" -verbose [myhostname[.sparsebundle
rsync'd to the remote linux server that us running netatalk3 to share that volume.
I am mounting it as afp://mylinuxbox/TimeMachineBackup
This all works, disk utility recognizeses and validates the disk.
Freshly erased:
641MB used, ~840GB available.
I unmount the disk and the sparsebundle.
I attemped a backup:
I go to Disk utility, mount the disk and it reports:
I repair the disk, says its ok and the disk space returns to "normal". I can repeat this process endlessly to the same result. No matter what I try (erasing, new sparsebundle, etc) TM always says it's on;y ~90GB free.

Actually, I can shorten this down to just:
Mount TimeMachineBackup disk, it reports ~95GB free.
Repair it, it reports 800+GB free
Unmount it
Remount it, it again reports ~95GB free.
Rinse. Repeat.

Similar Messages

  • Mobile Time Machine apparently increases free space

    After setting up Fusion Drive and restored OS and files, my MBP had 200GB of free space.
    Few days later, 230GB of free space in a Finder window.
    A week later, 300GB of free space, despite I did not delete fles that much.
    I checked "About This Mac">"Storage" for a week, and found that "Other" was decreasing (I did not delete much, again), and "Backups" was increasing.
    It is as if files which must be categoraized "other" are categoraized "Backups", and since the amount of "Backups" is not counted in Finder, apparently I had more and more free space.
    Have anyone experienced such strange case? I disabled mobile time Machine, fearing "other" files would be deleted as "backups" files would be.

    Actually, I can shorten this down to just:
    Mount TimeMachineBackup disk, it reports ~95GB free.
    Repair it, it reports 800+GB free
    Unmount it
    Remount it, it again reports ~95GB free.
    Rinse. Repeat.

  • Time machine not recognizing free space even though it "knows" about it

    Trying to back up to an external hard drive I'm getting this error from Time Machine when it tries to back up:
    "This backup is too large for the backup volume. The backup requires 52.5 GB but only 495.8 GB are available..."
    Clearly it KNOWS the space is there, but its math is wrong since it seem to think that 52.5 GB is greater than 495.8 GB.
    Suggestions?

    Sometimes, this error is legitimate. The user may not realize that they need to exclude additional hard disks that TM may be seeing. This is done in the “Options…” window of the Time Machine Preferences.
    Nevertheless, many times this error just doesn’t make sense, stating that not enough free space exists for a backup that is clearly smaller. (“The backup requires 45.9 GB but only 182.6 GB are available”)
    The answer and fix may have been discovered by a poster in the macosxhints forums: (http://forums.macosxhints.com/archive/index.php/t-84284.html)
    Essentially, while Time Machine DOES delete old backups from the sparsebundle, it DOES NOT free up the space occupied by those old backups. Eventually, "all previous backups were deleted and no space was gained. . . . What appears to be going on here is that the sparsebundle isn't self-shrinking - unused bands aren't being automagically discarded."
    The solution is to compact the TM backup sparsebundle in Terminal using:
    hdiutil compact yoursparsebundlefilename.
    He concludes, "I gained 30+gb of space on the backup volume by compacting that sparsebundle. And now TM runs just fine, since it has plenty of space."
    Obviously, this is a bug in TM. It does not appear to effect everyone, and only seems to appear under certain curcumstances.
    Let us know if this works for you.

  • How to speed up my system- reboot from time machine or increase free space?

    I've just upgraded my system to 3GB ram and some actions are being quite sluggish still- this I would suspect is because I have only 3GB free on my 120GB hard drive.
    Would rebooting the system from a time machine backup speed up the computer- in that all the files should be continuous or should I just aim to make more space on the hard drive?

    Ouch! You need to delete files - it's not a fragmentation issue, but a lack of available space for virtual memory and swap files. You should always have 10-15% of your capacity free (so, for you, that means keeping 11-16 GB free space on your drive).
    At this point, I'd recommend deleting files to free up space, then running Disk Utility > Verify Disk (and if errors are found, boot from the Install DVD and Repair Disk).
    To find your largest files, use something like Disk Inventory X:
    http://www.derlien.com

  • What items do you delete from backup on time machine to make more space available

    What items do you delete from back up on time machine to make more space?

    There's no need to do that unless Time Machine has reported a Disk Full alert. In this case you can:
    1. Delete older entries using the Time Machine application to free up sufficient space.
    2. Get a new and larger Time Machine backup drive to replace the old one.
    3. Erase the backup drive and start over.

  • Does backing up my hard drive to time machine gain me more space/speed on my iMac?

    I have an iMac. here are the specs:
    Hardware Overview:
      Model Name:    iMac
      Model Identifier:    iMac8,1
      Processor Name:    Intel Core 2 Duo
      Processor Speed:    2.8 GHz
      Number Of Processors:    1
      Total Number Of Cores:    2
      L2 Cache:    6 MB
      Memory:    4 GB
      Bus Speed:    1.07 GHz
      Boot ROM Version:    IM81.00C1.B00
      SMC Version (system):    1.30f1
      Serial Number (system):    QP921090ZE4
      Hardware UUID:    20AE2D9A-DB71-54DF-95F7-DAEFEE167723
    I have a TON of art/photos on this computer. I'm wondering if backing my hard drive up with time machine gains me more space and processing speed-or if it only slows my computer down? is it better to house my files on a seperate drive from the drive i am using for backing up with time machine?

    Just to add a little, Time Machine is not a storage drive. Backups on there are not in a form you can use as you would from your normal internal. If you delete your pics etc. after backup, they won't be backed up on subsequent runs, and will eventually be lost when the TM drive gets near full and starts deleting the oldest backups. Have a read of Pondini's TM articles; http://pondini.org/TM/Home.html
    To do what you want, you need another drive to which you can simply copy your pics etc and open from there while booted to your internal. (this is a basic storage drive)
    The storage drive can then also be backed up to TM (provided the TM disc is big enough).

  • Due to NAS issues, when I started a new time machine backup it did not have the old backups available. My question is do I need to delete them or will time machine automatically reclaim the space?  Only one Sparse Bundle, same name.

    Due to NAS issues, when I started a new time machine backup it did not have the old backups available. My question is do I need to delete them or will time machine automatically reclaim the space?  There is only one sparse bundle but when I enter time machine I don't see my historic backups.  I use a synology DS212 for my time machine.  Started a new backup which is 218gb but it says 618 gb is occupied  therefore it looks like 2 or 3 backups are still on the disk. Before my NAS issues the last backup was in 2014.  As you can see there is a second sparse bundle from 2012.  Not sure what that is.

    This is an old message now, but what happened to me similarly was:
    I had a major computer crash and through complicated pathways ended up reinstalling (Mavericks) as a new user (long story).
    At least I had good Time Machine backups on an NAS drive (Synology DS212j), or so I thought - when I started Time Machine up again, the old backup file was gone, replaced by a new one using my "new computer" name. The old file was gone both by directly mounting the NAS drive and by clicking "Enter Time Machine".
    It's like I had {OldShareName}.sparsebundle and then it was replaced by {NewShareName}.sparsebundle, all of the old info vanished.
    (I have spent a week finding old files elsewhere and have completed a satisfactory self-restore. It pays to "archive" [my own variation of] as well as "back-up".)
    My belief is that if this were a wired-netword-drive, e.g. plugged right into my iMac with a USB cable, then the old file would have remained.
    But this is an NAS drive, connected directly to my Airport wireless router, and I don't know the significance of the fact that it stores its Time Machine backups as "sparsebundle" files rather than simply as plain(er) files.
    As usual when things get complicated with computers (not just Apple computers) there was never a warning message. Something like "YOU'RE ABOUT TO DELETE A TIME MACHINE BACK-UP FILE!!!" would have made my life a lot simpler.
    BTW, I did try a "restore from Time Machine" option the first thing I had my "new computer" (old hardware, 2009 iMac) up and running, using Migration Assistant, and it ran for many hours and then failed in the wee hours - what that has to do with anything I'm not sure.
    I'm not sure that I have a question about this other than "why do these things happen to me?", but it's a warning. Apart from that I've been very happy with the stability and reliability (but not the cost or set-up complexity) of NAS vs. directly-cabled external drives.
    Charles

  • I am having problems with Time Machine and having enough space to finish my last back up.

    I am having problems with Time Machine and having enough space to finish my last back up.

    Take a look at this link, http://support.apple.com/kb/HT1427

  • Time Machine drive reporting more and more disk space available

    OK, so I've been using Time Machine since 28-OCT-2007 and all my backups are present. I have watched my TMDrive (Buffalo 500GB Fire Wire) report as little as 20GB available and slowly over the past 30 or so days report 205.42 GB now available. Any sizable downloading I do is pointed at another external HDD and that is listed in the Do NOt Backup list. I understand how hourly and daily works, but to see such drastic swing in available disk space seems a bit odd. Has anyone else seen this?
    Message was edited by: brenodo

    Brenodo,
    As backups are thinned, you will see a reduction in the amount of space used on the TM drive. This is entirely normal. Keep in mind that TM is designed to maintain a "restorable" copy of your system, and all of your user files, past and present. This represents a discreet amount of data which is only added to in small increments, really... as you say, any large downloads are going to a dedicated external.
    While TM might temporarily use much more disk space to manage its backups, the thinning process will eventually weed out everything that is unnecessary, as you are now seeing. I wouldn't be surprised if you begin to see the free space being used again, at some point, and the cycle will begin anew.
    Scott

  • Time Machine unable to free enough space

    Just returned from a longer trip, taking a lot of pictures, and now my Time Machine backup is failing. Here's what I can read from the logs:
    1) For about 45 minutes, it determines what needs backing up
    2) Then, it determines it doesn't have enough space
    3) It gets rid of a few backups (between 1 and 10), but still doesn't have the space
    4) It gives up
    This pattern has been repeating for days, once an hour, and no backup has happened.
    How can I recover from this?
    Here is the log of a run:
    Jan 14 02:47:06 weirdedmbp /System/Library/CoreServices/backupd[1931]: Starting standard backup
    Jan 14 02:47:06 weirdedmbp /System/Library/CoreServices/backupd[1931]: Backup destination alias resolved to path: /Volumes/Weird Ed's Time Capsule
    Jan 14 02:47:08 weirdedmbp /System/Library/CoreServices/backupd[1931]: Disk image /Volumes/Weird Ed's Time Capsule/WeirdEdMBP_001f5be6fa3e.sparsebundle mounted at: /Volumes/Backup of WeirdEdMBP
    Jan 14 02:47:09 weirdedmbp /System/Library/CoreServices/backupd[1931]: Backing up to: /Volumes/Backup of WeirdEdMBP/Backups.backupdb
    Jan 14 02:47:21 weirdedmbp /System/Library/CoreServices/backupd[1931]: Event store UUIDs don't match for volume: Macintosh HD
    Jan 14 02:47:21 weirdedmbp /System/Library/CoreServices/backupd[1931]: Node requires deep traversal:/ reason:kFSEDBEventFlagMustScanSubDirs|kFSEDBEventFlagReasonEventDBUntrustable|
    Jan 14 03:31:54 weirdedmbp /System/Library/CoreServices/backupd[1931]: Backup destination alias resolved to path: /Volumes/Weird Ed's Time Capsule
    Jan 14 03:31:55 weirdedmbp /System/Library/CoreServices/backupd[1931]: Disk image /Volumes/Weird Ed's Time Capsule/WeirdEdMBP_001f5be6fa3e.sparsebundle mounted at: /Volumes/Backup of WeirdEdMBP
    Jan 14 03:35:50 weirdedmbp /System/Library/CoreServices/backupd[1931]: Starting pre-backup thinning: 52.66 GB requested (including padding), 16.57 GB available
    Jan 14 03:38:15 weirdedmbp /System/Library/CoreServices/backupd[1931]: Deleted backup /Volumes/Backup of WeirdEdMBP/Backups.backupdb/WeirdEdMBP/2008-12-10-003030: 16.57 GB now available
    Jan 14 03:39:01 weirdedmbp /System/Library/CoreServices/backupd[1931]: Deleted backup /Volumes/Backup of WeirdEdMBP/Backups.backupdb/WeirdEdMBP/2008-12-18-235052: 16.57 GB now available
    Jan 14 03:39:33 weirdedmbp /System/Library/CoreServices/backupd[1931]: Deleted backup /Volumes/Backup of WeirdEdMBP/Backups.backupdb/WeirdEdMBP/2008-12-18-225055: 16.57 GB now available
    Jan 14 03:40:04 weirdedmbp /System/Library/CoreServices/backupd[1931]: Deleted backup /Volumes/Backup of WeirdEdMBP/Backups.backupdb/WeirdEdMBP/2008-12-18-215132: 16.57 GB now available
    Jan 14 03:40:48 weirdedmbp /System/Library/CoreServices/backupd[1931]: Deleted backup /Volumes/Backup of WeirdEdMBP/Backups.backupdb/WeirdEdMBP/2008-12-18-204435: 16.57 GB now available
    Jan 14 03:40:48 weirdedmbp /System/Library/CoreServices/backupd[1931]: Stopping backup.
    Jan 14 03:40:54 weirdedmbp /System/Library/CoreServices/backupd[1931]: Backup canceled.
    Jan 14 03:41:01 weirdedmbp /System/Library/CoreServices/backupd[1931]: Ejected Time Machine disk image.
    Jan 14 03:41:01 weirdedmbp /System/Library/CoreServices/backupd[1931]: Compacting backup disk image to recover free space
    Jan 14 03:42:12 weirdedmbp /System/Library/CoreServices/backupd[1931]: Completed backup disk image compaction

    Right, I understand that there isn't enough space, but I also was under the impression that Time Machine is supposed to manage the space. The backups are the only thing on the time capsule. I'm backing up a single MacBook Pro with a 200GB drive to the 500GB time capsule, so Time Machine should be able to make space by simply deleting old backups. An so far, that has worked.
    I get the impression that there's a limit to how many old backups are being removed, and it feels like a time limit. Meaning: If TM deletes backups for more than 10 minutes or so, and there's still not enough space, it gives up.
    Trouble is that each turn of deleting some old backups is preceeded by that ~45 minute period of "determining what to back up".
    That's what I'm doing now: Deleting old backups, and once that completes I'll compact the sparse bundle. Hopefully, that'll do the trick. So if I let this go on for days/weeks/months, it probably will eventually free up enough space again.
    Still, this would seem like a rather common case, this should really work. So far, not very impressed with Time Machine.

  • 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

  • Difference in reporting free space on my drive

    Hi all,
    I have a macbook pro 2011 running Lion on a 500GB HDD. I am having a small issue in reading how much free space do I have on my hard drive.
    The status bar in the Finder window reports:
    DiskUtility.app reports:
    I don't have any partitions on the hard drive (other than what Lion creates on it's own) and "Macintosh HD" is the only drive I have. I do use time machine and I have already disabled local backups but the difference in free space stays. I am just not sure what is causing this huge difference. If it was a couple of GBs I'd happily ignore but this is more than 80GB.
    Any idea?

    malikons wrote:
    the next day Finder synced with DiskUtility automagically. I think it takes time to remove the local backups.
    Yes, especially on a busy system, and if there were a lot of files involved.
    I rebooted my macbook into recovery mode and fixed the hard drive errors. So, I believe, fixing the HDD errors and disabling local backups eventually fixed the issue.
    Yup, directory errors can cause all sorts of weirdness. 

  • Time machine files and disk space warning.

    hello, i have ran into some unknown issues with my os x and even though there have been similar topics discussed i would like to address mine and i hoe someone can help me out.
    1. I am not sure if I accidentally turned on time machine or not , but at some point when i restarted a computer i noticed different folders and files that i have not created myself on my HD such as
    .com.apple.timemachine.supported
    .fseventsd
    .hotfiles.btree
    .Spotlight-V100
    .Trash
    .vol
    var
    etc
    tmp
    I do not know if this folders are safe to delete, since i am not using time machine.
    2. Trying to download rather big file 34gb i received numerous warnings that my disk isfull, and it is not. i have 105GB used and 126GB free, also I am using 4gb RAM. so there should not be a problem. I saw a few topics regarding disk space warning, that were suggestinng that the user runs an application which shows where most of HD is used.
    I cleaned a few stuff, but still, how can I prevent from this warning to appear.
    Thank you for any suggestions

    can i hide them?
    Update: found terminal command to hide the successfully.
    i ran verify disk and verify disk permissions and everything is OK.
    following reports were made:
    Verifying volume “Macintosh HD”
    Performing live verification.
    Checking Journaled HFS Plus volume.
    Checking Extents Overflow file.
    Checking Catalog file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    Checking Extended Attributes file.
    Checking volume bitmap.
    Checking volume information.
    The volume Macintosh HD appears to be OK.
    Verify permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
    Permissions differ on "Library/Preferences", should be drwxrwxr-x , they are drwxrwxr-- .
    Permissions differ on "Library/Application Support", should be drwxrwxr-x , they are drwxrwxr-- .
    Permissions differ on "Developer/Examples/JavaWebObjects/DataBaseSetUp/dbdump.sh", should be -rw-rw-r-- , they are -rwxrwxr-x .
    Permissions verification complete
    Repairing permissions for “Macintosh HD”
    Reading permissions database.
    Reading the permissions database can take several minutes.
    Permissions differ on "private/var/log/secure.log", should be -rw------- , they are -rw-r----- .
    Permissions differ on "private/var/spool/cups/cache/rss", should be drwxr-xr-x , they are drwxrwxr-x .
    Permissions differ on "Library/Preferences", should be drwxrwxr-x , they are drwxrwxr-- .
    Permissions differ on "Library/Application Support", should be drwxrwxr-x , they are drwxrwxr-- .
    Permissions differ on "Developer/Examples/JavaWebObjects/DataBaseSetUp/dbdump.sh", should be -rw-rw-r-- , they are -rwxrwxr-x .
    Permissions differ on "Developer/Examples/JavaWebObjects/DatabaseSetup/dbdump.sh", should be -rwxrwxr-x , they are -rw-rw-r-- .
    Permissions repair complete
    still bugs me why i am getting this warnings, nothing today but you never know when next one will pop...
    Message was edited by: g3m1nn1
    Message was edited by: g3m1nn1

  • HT203177 how do i clear old backups from time machine to make more space

    My 2TB Time Machine is nearly full.  I am trying to back up a drive in a Mac Min that is starting to fail and wanted to do so on Time Machine.  Unfortunately since my Time Machine is nearly full it will not back up drive without eliminating nearly all of the files on this Mini.  I am okay overwriting the other backups already on the Time Machine but do not know how to force Time Machine to do so.  Please any clues on how to make Time Machine overwrite other backups would be greatly appreciated.

    About TM "Backup Drive is Full" Alert
    TM only deletes older files if they have been deleted from the source and when TM needs space on the backup drive for a new incremental backup. Time Machine "thins" it's backups; hourly backups over 24 hours old, except the first of the day; those "daily" backups over 30 days old, except the first of the week. The weeklies are kept as long as there's room.
    So, how long a backup file remains depends on how long it was on your Mac before being deleted, assuming you do at least one backup per day. If it was there for at least 24 hours, it will be kept for at least a month. If it was there for at least a week, it will be kept as long as there's room.
    Note, that on a Time Capsule the sparsebundle grows in size as needed, but doesn't shrink. Thus, from the user's view of the TC it appears that no space has been freed, although there may be space in the sparsebundle.
    Once TM has found it cannot free up enough space for a new backup it reports the disk is full. You can either erase the backup drive and start your backups anew or replace the drive with a larger drive.
    As you can see Time Machine does prune old backups to make space, but eventually it may no longer succeed. Then you will get the alert. You can delete old backups if you wish, but only using the Time Machine application.

  • Time Machine not freeing up space with manual delete of old backups

    I have time machine backing up an external RAID to a Drobo with 7.2TB of total space.  The total backup size as estimated by TM is 4.6TB.  This setup was running fine for me for a while, until I added some internal drives full of data to my Mac Pro, and forgot to tell TM to exclude them.  I didn't realize this until TM told me my backup disk was full.  Fine, so I excluded those drives, and then deleted all backups of those drives, as well as going back and deleting quite a few old backups in their entirety.  I even went and found about 500GB of data that I no longer needed, deleted it from my RAID and then again deleted all backups of that folder from TM.  But after all this, my drive still only has about 70GB of free space on it.  When I know at a minimum there should be 500GB free, if not 1-2TB free after all that spring cleaning.  How can I get that free space back?  It seems as if TM is holding it hostage.  I should add that slowly over the few days since deleting, my Drobo free space slowly creeps up.  Maybe about 10GB every hour when I go and check free space available.  Is this just TM taking forever to delete the old backups, even after the computer has been restarted, shut down, etc. multiple times?
    I really don't want to have to erase the entire TM drive and start over, as it takes days to backup 4.6TB of data and slows down my whole system.  Any help is appreciated!

    I have no direct experience with a Drobo, but in many threads about them, as with many other 3rd-party NASs, either the built-in software creates a sparse bundle, or the instructions have the user do so.
    But yes, a sparse bundle is a sparse bundle is a sparse bundle , so if you can locate it via the Finder, and have permission to it, you should be able to compact it manually, per those instructions.
    If not, you'll have to talk with the Drobo folks.

Maybe you are looking for