2

I have a system that continually runs out of disk space. Im going to write a script that cleans up directories that grow larger. Usually these are log directories. Given the nature of the machine, i dont need to keep logs.

I want to write a script that shows me all the directories that are increasing in size, so i can make sure this list goes to 0.

I am thinking something like this

1. du /
2. wait 24 hrs
3. du /
4. find all instances where the file size increased

It looks simple enough, but my issue is that du works on files and directories, you cant do it on only dirs. How can i overcome that?

5 Answers5

5

You could use find to tell whats been modified in 24 hours, 

find / -type d name \* -mtime 1 -print

Should list all directories that have changed in the last 24 hours, but remember, realistically its files that change rather than the directories.

Another way would be to do

du -s *  | sort > currentsize

This summerises by directory, and files in the starting location, but, you then could store it each day, move that file to say oldsize, run the command again

then

diff currentsize oldsize

you can see whats changed.

You could use awk to decide if one is bigger or smaller..

All system logs tend to to change too.

But the original find I stated shows you files altered in the last 24 hours. You could also use something based on that.

BugFinder
  • 161
  • 3
3

If your problem is with log files, may I suggest using logrotate instead?

It has the capability of periodically 'zero'-ing log files, archiving and/or deleting old logs, and so on. Even to the point of stopping the related daemon before doing its magic (might be necessary if said daemon keeps the log file open).

pepoluan
  • 5,038
  • 4
  • 47
  • 72
  • 1
    You mean restarting, not stopping. Even after logrotate renamed or even deleted a file, the daemon process keeps writing to the same file (if you deleted it, it disappeared from the directory but it is not unlinked yet from the filesystem or respectively, if you renamed it, the renamed file continues to grow). A restart forces the daemon to drop its hold on the file. – nalply Jul 28 '11 at 05:53
  • @nalply well, a 'restart' is technically a 'stop' followed by a 'start'. I meant 'stop' not 'pause'. But your explanation helps in highlighting why the daemon needs to be stopped. – pepoluan Aug 08 '11 at 04:29
0

It's not terribly efficient, but you can do something like this:

find / -type d -print0 | xargs -0 du -s
Greg Hewgill
  • 6,849
  • 3
  • 30
  • 26
0

Assuming you're trying to find the growing directory under /, you can try:

du -s /*/

This will output summarized individual sizes for each directory under / (and only directories).

Costi Ciudatu
  • 101
  • 2
  • this sort of works, i will be doing a lot of double work though. so i could do it on root, find the top level dirs that increased, then go down and down and down and recursively find the invididual dirs that changed. but i will be repeating quite a lot of work. –  Apr 11 '11 at 21:13
0

As already noted use logrotate to manage log file rotation and cleanup. It can compress old logs, and remove oldest logs after X generations.

My usual search for space runs using walking the largest directories using the command du -s * | sort -n. This allows me to quickly find directories and files where cleanup will have a major impact.

If you are using munin to monitor disk usage you can configure it to notify when usage is high. 80% and 90% are a good starting point for warning and critical messages.

You run find on a periodic basis to find files larger than some threshold. This won't help if you have a lot of largish files, but will detect files growing unreasonably large.

BillThor
  • 27,737
  • 3
  • 37
  • 69