There’s a new way to vote in the Apple Support Community!

You can now upvote or downvote replies and User Tips, depending on whether or not they’re helpful. Learn more about the recent changes to the way you can Vote in the Apple Support Community.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Finder says Home Disk is full, utilities say I've only used 93Gb of 232Gb

Earlier this evening I all of a sudden got an alert that my disk was full, 232Gb. 0Gb remaining.

It said I needed to renove some files. I tried. I removed about 10 Gb, but it didn't give me any more space.

I booted from my Clone to to see if I could run dik utility repair. It came up saying the disk was fine.

Repaired Permissions. Everything came up OK there too.

I ran Disk Warrior from it;s disk and it came up stating that I was only using 93Gb of 232Gb. (Which is what I remembered and was about how much my recent Carbon Copy Clone added up to)

I tried WhatSize and it said the same. I'm currently waiting for a license for Tager Cache Cleaner to see if it will help. None of the utilities is finding any hidden large files.

I've also tried backing up the mail folder and removing Envelope Index, but, of course, that made Mail crash since it's being told there's no room on the hard drive. I'm totally stumped.

I imagine there's some corrupt file somewhere, but I'm not getting a fix on it.

Recent changes to the drive - I upgraded to 10.4.9 a few ays ago. Had to install a third party driver for my HP PSC 2175 - hpijs-foomatic-2.0.2.

Printer stopped working earlier today and I had to reinstall CUPS and then the driver again before printer would work. Sortly thereafter that I got the error message about disk full.

System info:
Machine Name: Power Mac G5
Number Of CPUs: 1
CPU Speed: 1.6 GHz
L2 Cache (per CPU): 512 KB
Memory: 2 GB
Bus Speed: 800 MHz
Boot ROM Version: 5.1.5f2


I have several different firewire drives attached as well as a USB "jump" drive.

Any advice would be most appreciated.

G5 1.6Gz Mac OS X (10.4.8)

Posted on Jun 6, 2007 10:26 PM

Reply
11 replies

Jun 7, 2007 12:24 AM in response to matthewcostello

Take a look at this article I wrote:

http://www.pinkmutant.com/articles/TigerMisc.html

See if it helps. Be sure to check out the information about the /private/var/spool/cups folder and the possiblity of a giant tmp folder there (the article includes instructions on how to get there and a link to help you get rid of the problem).

If everything checks out OK (that is, even the Terminal commands don't find any giant strange file/folders and return the same information about the drive) then the problem would be something wrong somewhere in the Finder.
Francine

User uploaded file
Francine
Schwieder

Jun 7, 2007 8:02 AM in response to Francine Schwieder

OK I found the offending folder.
/private/var/spool/cups has 138G:

mcg5:~ matthewcostello$ sudo du -cxhd 1 /private/var/spool
138G /private/var/spool/cups
4.0K /private/var/spool/fax
0B /private/var/spool/lock
4.0K /private/var/spool/mqueue
0B /private/var/spool/postfix
0B /private/var/spool/samba
138G /private/var/spool
138G total


But when I look in the directory it doesn't give me any detail where the space is being used:

mcg5:~ matthewcostello$ sudo du -cxhd 1 /private/var/spool/cups
8.0K /private/var/spool/cups/cache
0B /private/var/spool/cups/tmp
138G /private/var/spool/cups
138G total

When I try to run the commands from the link here:

http://docs.info.apple.com/article.html?artnum=107990

I get "permission denied."

What am I missing?

Thanks for your help.

Jun 7, 2007 10:03 AM in response to matthewcostello

I figured out I was not writing the commands properly from
http://docs.info.apple.com/article.html?artnum=107990

I was able to successfully execute them. However, it didn't win back my disk space. I was able to remove some more files and gained 12 G.

But it appears there's a there's a big space being used in /private/var/spool/cups which I don't understand how to remove.

Thanks for any help anyone has to offer.

G5 1.6Gz Mac OS X (10.4.8)

Jun 7, 2007 11:43 AM in response to Francine Schwieder

There are hundreds or more repeating files as follows:
-rw-r----- 1 root lp 1M Jun 6 19:09 00010e54
-rw-r----- 1 root lp 1M Jun 6 19:09 00010e55

<snip>

-rw-r----- 1 root lp 1M Jun 6 19:47 00013030
-rw-r----- 1 root lp 1M Jun 6 19:48 00013031
-rw-r----- 1 root lp 1M Jun 6 19:48 00013032
-rw-r----- 1 root lp 1M Jun 6 19:48 00013033
-rw-r----- 1 root lp 1M Jun 6 19:48 00013034

and then this final three.
-rw------- 1 root lp 23K Jun 6 18:05 c00097
drwxrwxr-x 5 root lp 170B Jun 6 20:02 cache
drwxrwx--T 2 root lp 68B Jun 7 12:57 tmp

Obviously the repeating 1M files are the culprit. They don't show up in the finder when I use a Go to file command. They don't show up in Disk Doctor, WhatSize or any other utility I've found. Only via the terminal using UNIX commands.

Since I'm not that versed in UNIX, is my next step to remove them one by one?

I really appreciate your help.


G5 1.6Gz Mac OS X (10.4.8)

Jun 7, 2007 12:20 PM in response to matthewcostello

I just found this discussion at the MacFixIt forums. You might read it carefully, and also take a look at the MacOSXHints article mentioned:

http://www.macosxhints.com/article.php?story=20070319143243249

I have a batch of those job history files as well so thought I would try removing them and see what happened. I first got myself a root shell:

NoobiX:~ francine$ sudo -s

Hit return and entered my password, hit return again, then changed directory:

NoobiX:~ root# cd /private/var/spool/cups

Hit return and ran a list command:

NoobiX:/private/var/spool/cups root# ls -al
total 304
drwx--x--- 41 root lp 1394 Mar 26 21:59 .
drwxr-xr-x 7 root wheel 238 Aug 3 2006 ..
-rw------- 1 root lp 3571 Aug 24 2006 c00001
-rw------- 1 root lp 3574 Aug 24 2006 c00002
-rw------- 1 root lp 3505 Dec 8 00:24 c00003
....and so on.... down to
-rw------- 1 root lp 3531 Mar 26 21:59 c00038
drwxrwx--T 2 root lp 68 Dec 21 22:37 tmp

Which verified I was in the right place. I tried removing just one of the files:

NoobiX:/private/var/spool/cups root# rm c00001

which worked fine. I then decided doing this would be tedious, so tried this:

NoobiX:/private/var/spool/cups root# rm -r *

There is a space between the rm and -r and after -r before the * (a wildcard). That was probably a mistake since it not only nuked the history files but also the tmp directory. I should have probably used something like rm -r "c*" (since all the history files begin with c that should have got them and spared the tmp folder). I tried recreating the tmp folder with this:

NoobiX:/private/var/spool/cups root# mkdir tmp

Which seemed to work:

NoobiX:/private/var/spool/cups root# ls -al
total 0
drwx--x--- 3 root lp 102 Jun 7 12:00 .
drwxr-xr-x 7 root wheel 238 Aug 3 2006 ..
drwxr-xr-x 2 root lp 68 Jun 7 12:00 tmp

But being a suspicious sort I ran Disk Utility to Repair Permissions and it did indeed report an error on the /private/var/spool/cups/tmp folder, but it did repair the permissions on the folder successfully, so I'm assuming all is now OK. Of course, I haven't actually tried printing anything yet...

If you choose to try this after you finish type exit and hit return to kill the root shell, then quit Terminal.
Francine

User uploaded file
Francine
Schwieder

Jun 7, 2007 12:54 PM in response to Francine Schwieder

PS--Just did some experimenting and discovered the only way to mass delete files in a folder, without deleting the sub-folders, is to use a find/rm combo command. The rm command doesn't support wildcards beyone the simple * (everything). Thus I would have had to do something like this to mass delete the files and leave the tmp folder:

find . -name "c*" -exec rm -rf {} \;

This says "find in the current folder all files whose name begins with c and then delete them." You could also run rm interactively:

rm -ri *

It will then ask you for each item if it should be removed. You type either a y for yes or n for no and hit return. This too would be pretty tedious.
Francine

User uploaded file
Francine
Schwieder

Jun 7, 2007 3:06 PM in response to Francine Schwieder

Francine
the only way to mass delete files in a folder, without deleting the sub-folders, is to use a find/rm combo command
Um, if you leave out the "-r", it will not delete any folders.
<pre>

DESCRIPTION
The rm utility attempts to remove the non-directory type files specified
on the command line.

</pre>So, all matthew needs is

sudo rm /var/spool/cups/000*

on the assumption all his 1MB files start with three zeroes.

Jun 7, 2007 8:20 PM in response to Francine Schwieder

Thanks so much to both of you.

I find UNIX an elegant and succint language. I've just never had an opportunity to spend much time with it (unless it's an emergency, like this).

The knowledge you've given me has saved me hours and has been shared in a clear manner.

I agree - sudo also makes me nervous, but what makes me more nervous is that in the course of a few minutes, some stray programming command made enough 1M files to eat up 138G of space that only shows up in the terminal!.

Obviously something happened when I was re-installing CUPS and the other printer driver. I just don't know what.

Again, I appreciate your help and I'm pretty sure I have a strong enough handle to complete the process, so I'm calling this solved.

If I need more, you'll hear from me.

Be well,

Matthew

G5 1.6Gz Mac OS X (10.4.8)

Jun 8, 2007 8:39 PM in response to matthewcostello

Just wanted to post an update in case anyone else comes up agaist this problem.

I was faced with literally thousands of 1M fules and how to get rid of them.

Where Michael's suggestions seemed to be correct, it didn't work when I tried it. I would get a "No such file or directory" message.

As Francine suggested, I had to go down to the root and use the CD command to be inside the directory . I was careful to check that any rm command I was going to use could be mirrored as an ls command first.

mymac:/private/var/spool/cups root# ls 000*

Unfortunately when I tried this wildcard combination I got a report that there were too many arguments. So I decided to go at it in more manageable chunks.

Filenames were 8 characters long like this 00012fef

so I started by using this combination:
mymac:/private/var/spool/cups root# ls 0001*

This worked. I saw a increase of about15G in my hard drive space. So I kept going with a series like this:

mymac:/private/var/spool/cups root# rm 0000f*
mymac:/private/var/spool/cups root# rm 0000e*
mymac:/private/var/spool/cups root# rm 0000d*
mymac:/private/var/spool/cups root# rm 0000c*
mymac:/private/var/spool/cups root# rm 0000b*
mymac:/private/var/spool/cups root# rm 0000a*
mymac:/private/var/spool/cups root# rm 00009*
mymac:/private/var/spool/cups root# rm 00008*
mymac:/private/var/spool/cups root# rm 00007*
mymac:/private/var/spool/cups root# rm 00006*
mymac:/private/var/spool/cups root# rm 00005*
mymac:/private/var/spool/cups root# rm 00004*
mymac:/private/var/spool/cups root# rm 00003*
mymac:/private/var/spool/cups root# rm 00002*
mymac:/private/var/spool/cups root# rm 00001*
mymac:/private/var/spool/cups root# rm 00000*

Anyway, I regained my 138G.

I hope this is helpful to someone.

Be well.

G5 1.6Gz Mac OS X (10.4.8)

Finder says Home Disk is full, utilities say I've only used 93Gb of 232Gb

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.