Disc Space near 80% (noob question)

[spr]

I'm using over 10GB of disc space while my current site + database is just about a few hundreds MB. So I wonder if it's the log files or some other junk stuffs that accumulated over time.

How should I find out and clean up those files to clean my disc space?

Any suggestion is greatly appreciated,
spr

[MundoNetwork]

do you have awstats, webalizer or analog statistics software enabled?

[Vin DSL]

How should I find out and clean up those files to clean my disc space?

Any suggestion is greatly appreciated...

Do a 'DU'.

Shell works best, but it's also available via cPanel...

As MundoNetwork implied, the 'stats' are probably eating up your disk space!

[Vin DSL]

do you have awstats, webalizer or analog statistics software enabled?

I *think* these proggies are enabled by default on all shared accounts, except VPS. They operator invisibly in the background.

Matter of fact, I don't know if you can even disable them. I've deleted the folders before, only to have them return automagically in the future.

[spr]

Thanks guys, especially for the "DU" command, I found out my apache log file was eating up some GB of my space, now it's back to 10%. Can't believe that log file got 70% of my disc space.

Well, it's all good now.

[Ron]

You must have a hugely busy site for the logs to take up that much space!

You can disable the saving of logs through CPanel if you really want to.

[thisisit3]

My signature points to various interesting stuff, one of those explains a bug in cPanel/WHM which allows the apache logs to become huge on busy servers. In there i explain how to fix the problem by adding the apache logs in the logrotate configs.

Logs and logrotate:
Logs and logrotate - important fix

Clean your /var/log/messages
Clean your /var/log/messages, move ftp logs to /var/log/ftp

etc.

[spr]

Actually I was having problems with eAccelerator, that's why the error was building up.
I fixed that by "chmod 0777 /opt/lampp/tmp/eaccelerator" (yah, i'm using lampp)

The log file is back to normal now.

[R45]

du -h --max-depth=1

Is really easy to use, and just work into the subdirectories to find offenders.

If you use any decent amount of MySQL, the bin-log is a massive contributor to disk space. Consider capping its size in your mysql configuration.

[thisisit3]

I don't think the Binary Log (mysql 4.1.3 or newer only) is enabled by default, so its not something most people will want to look for.