Benches macOS

14

Disk Full But It Isn't

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Helping a friend with her MacBookPro 160 GB HD. Finder shows 148 GB total size - 146 GB used 2 GB free. She gets "Disk Full..." messages a lot. We ran WhatSize on it and it reports total file usage of 80GB - so there should be sub80 free. But the Finder disagrees. And WhatSize sees all the invisible files - "bin", "var", "mach_kernel" etc. so I don't think we are missing any. We'd rather not do the obvious - full backup, reformat, reinstall but, unless there is an option, that's what we'll do. Is there a way/tool to get Finder to recatalog/reindex the drive?

14 replies

Sign in or join Beachball Help to reply.

  1. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    A simple restart can free up memory that's been allocated for ram.

    How much ram do you have? If you don't have a lot of ram but keep open lots of ram hogging apps at the same time vertual memory can eat up disk space. It's supposed to let it go when you quit the app but doesn't always. Restarting would fix it.

    One nice little trick is to make a clone of the hard drive using Carbon Copy Cloner or SuperDuper! (I favor CCC lately). Then clone in reverse, from the clone to the HD. This is a cheap and easy way to optimize the hard drive which would free up space.

    You can also do an Erase and Install then Migration Assistant to migrate files, apps and settings back from the clone.

    Hard to say which is better, I would do the re-cloning first, but you'll need another HD at least as big as MacBook's.

    If you still don't have much disk space then I'd say Watsize is wrong or you are reading it wrong.

  2. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Kevin, if we go through the folders and GetInfo on each we get the same#, more or less, as does WhatSize. The MBP has 4 GB ram. We have restarted. At one point we deleted about 1GB files to get 3GB free, then restarted and found there we only 1.5GB free! Clearly something is amiss in the OS. I was just hoping I could find a tool to fix this rather than the SuperDuper Clone then restore route.

  3. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I guess in a nutshell the Finder is doing this - 20 + 10 + 40 + (invisible 10) = 146.

  4. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Do you have FileVault turned on?

  5. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    No. Never used it. Interesting to note that an Apple "Genius" recommended this lady buy a large external drive - and this was after he did the "2+2=12" math himself.

  6. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    If you have Disk Warrior you can try running that to repair the directory. If not then just start up off the install disk and run repairs, it's not as good but it might be all you need. Then restart normally and run repair permissions.

    Other than that I would say do an archive and install or an erase and install with migration assistant. Be sure you have the clone or some kind of back up (Time Machine?) before getting started.

    It would be interesting to clone the drive and see how much space the clone uses up. Under normal circumstances you should get an extra 20 GB on the cloned version just by getting rid of any fragmentation of the disk by cloning.

  7. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    She runs scheduled SuperDuper backups nightly- they run about 80Gb. She had been doing Erase and Backup so each night she got a fresh copy of her entire machine - just 60 or GB smaller than the Finder thought it was.

  8. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    whatsize should give you more info than just the total amount of data on the drive. it can tell you what exactly is taking up all the space. You can also try one of these utilities:
    [Omindisksweeper|http://www.omnigroup.com/applications/omnidisksweeper>, [Disk Inventory X|http://www.derlien.com> or [Grandperspective|http://sourceforge.net/projects/grandperspectiv>. there is also a terminal method described on [this page|http://homepage.mac.com/francines/articles/TigerMisc.html].
    Also since you have superduper backups one easy thing to do would be to boot from the clone, reformat the main drive and clone the clone back.

  9. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Since she has the SuperDuper back up then cloning back to the hard drive seems like the best thing to do, then you'll have 80 GB back on the Mac.

    Seems like she must have a directory problem that is not reading info correctly or perhaps is not optimizing on the fly like it's supposed to.

    There is still the possibility you'll clone the problem back so keep an eye on the Mac to see if the numbers climb back up again. If they do then do an Erase and Install and migrate all the info and apps from the clone. Much less likely to copy the problem back that way.

  10. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    The whole issue is that nothing is taking up the space. WhatSize reports 80ish GB which is more or less what we get when we manually GetInfo all the folders at the root level. Clearly we do not see the hidden system files - WhatSize does - and in both cases we fall about 60GB short. What I was hoping for the existence of was a tool that could "encourage" the Finders view of the disk contents to update.

  11. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    just reformat the drive then and clone the clone back. If it's a weird problem with the filesystem it will go away. there are no tools to show space that's not actually there.

  12. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    That is now the plan - that is the easy part. The hard part is convincing the user that this will work, that it is OK, that all will be well, that her data will be preserved etc.

  13. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    just boot from the backup first and check that everything is there. This should be done anyway to make sure that the backup is good.

  14. 0

    Apple Support Community member

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Tell her this is the whole reason she's been doing all these backups for.