Disk full or not? [SOLVED]

[AS]

3.2G    var/

this is the 'problem': enter /var and type the commands:

cd /var
du -sch *

[muungwana]

/var  folder is taking 3.2GB !!!!!

what do you have in there? go there with a torch, a hammer and disinfectants, somebody is laying eggs in there 

[Bald Brick]

omskates,

You've probably set up Synaptic to leave downloaded packages in the cache. This makes sense if you have lots of disk space. If you don't, it doesn't.

You can remove the packages from within Synaptic or by running "apt-get clean" in a terminal as root. (If there are any rpms that you feel you may need, back them up first. Normally you don't need old rpms.)

[OMSkates]

/var  folder is taking 3.2GB !!!!!

what do you have in there? go there with a torch, a hammer and disinfectants, somebody is laying eggs in there  

You're funny, LOL

3.2G    var/

this is the 'problem': enter /var and type the commands:

cd /var
du -sch *

Code: [Select]

51M     cache
644K    db
4.0K    empty
153M    lib
4.0K    local
12K     lock
6.1M    log
4.0K    ltris.hscr
0       mail
4.0K    nis
4.0K    opt
4.0K    preserve
284K    run
3.0G    spool
0       tmp
8.0K    www
4.0K    yp
3.2G    total


omskates,

You've probably set up Synaptic to leave downloaded packages in the cache. This makes sense if you have lots of disk space. If you don't, it doesn't.

You can remove the packages from within Synaptic or by running "apt-get clean" in a terminal as root. (If there are any rpms that you feel you may need, back them up first. Normally you don't need old rpms.)

Thanks for your response.  I've run apt-get clean and autoclean quite a bit.   I havn't intentionally set up synaptic to save in the cache, I'll look at settings.

[muungwana]

http://tldp.org/LDP/sag/html/var-fs.html

The above link explains what each folder in /var is for.

I think you can safely delete everything in the folder and reclaim the space. look around and check where the eggs are laid and what process is laying them and try to see if you can have an adult conversation with it.

The space is probably due to a mis configured service and the folder will start gaining weight again if you dont fix whatever process is causing the problem

what does this command give you, as root again

cd /var/spool
du -sch *

You can run the command on all subsequent folders on your way to the folder where most of the space is taken and the name of the folder will give you a clue of what process is responsible.

[Old-Polack]

omskates:

You have 3 GB of something in /var/spool... I have 48 KB

[OMSkates]

The space is probably due to a mis configured service and the folder will start gaining weight again if you dont fix whatever process is causing the problem

what does this command give you, as root again

cd /var/spool
du -sch *

Thanks for the link; what a great reference!

Code: [Select]

16K     anacron
8.0K    at
4.0K    cron
3.0G    cups
4.0K    lpd
4.0K    mail
4.0K    repackage
4.0K    samba
3.0G    total

I looked with konquerer superuser mode; Why would cups have 3.0G ? There's like 70 files in /var/spool/cups of 700 to 800kb and bigger, just a whole crap-load of old printer jobs.

[AS]

may be... interrupted print jobs ?        you can verify with:
lpstat -t

or if not, post the content of (or part of) the folder:
ls /var/spool/cups

[OMSkates]

may be... interrupted print jobs ?        you can verify with:
lpstat -t

or if not, post the content of (or part of) the folder:
ls /var/spool/cups

That looks to be the case.

Code: [Select]

c00001  c00009  c00017  c00025  c00033  c00041  c00049  c00057      d00031-001
c00002  c00010  c00018  c00026  c00034  c00042  c00050  c00058      d00032-001
c00003  c00011  c00019  c00027  c00035  c00043  c00051  c00059      d00033-001
c00004  c00012  c00020  c00028  c00036  c00044  c00052  c00060      d00044-001
c00005  c00013  c00021  c00029  c00037  c00045  c00053  c00061      d00045-001
c00006  c00014  c00022  c00030  c00038  c00046  c00054  c00062      d00046-001
c00007  c00015  c00023  c00031  c00039  c00047  c00055  c00063      tmp/
c00008  c00016  c00024  c00032  c00040  c00048  c00056  d00026-001

Should not be an issue to clear the directory /var/spool as far as I can tell.
So just do a

Code: [Select]

rm /var/spool/cups/*??  then restart the cups server?

[muungwana]

it should be:

rm -rf /var/spool/cups/*

it shouldnt be necessary to restart cups server.

You can monitor the folder from now on to see if it will start to grow again and maybe see why cups put things in there, it could be because it was configured by default or by you to do that or your using it causes it to do that.

[OMSkates]

it should be:

rm -rf /var/spool/cups/*

it shouldnt be necessary to restart cups server.

You can monitor the folder from now on to see if it will start to grow again and maybe see why cups put things in there, it could be because it was configured by default or by you to do that or your using it causes it to do that.

Thanks so much for your help...all of you