/usr has grown 20% since Friday

[Patrick Scherrer]

My /usr filesystem has grown about 20% since friday. du -sk or searching /usr -size +10000 hasn't revealed any clues to help solve the problem.

Any ideas?

[Pete Randall]

Search for recently modified:

find /usr -mtime -1


Pete

[Patrick Scherrer]

That simply yields a couple of files that temporarily store output from some scheduled jobs. Small stuff in /usr/local/bin

[Adam W.]

Patrick,
I love referencing this I use it A LOT!!!!

To remove dated files. Can be modified to remove sized files as well.


# touch -amt 200504150000 /tmp/ref1
# touch -amt 200802282359 /tmp/ref2

# find /opt/mtmc/ibs/import/reject -xdev -type f -newer /tmp/ref1 -a ! -newer /tmp/ref2 -exec rm {} \+

This will remove files that are newer (more recently modified) than April 15 at 0000 AND NOT newer than Feb, 28th 2359 of this year, modofy the times as needed, here is a bit of a guide.

time Use the specified time instead of the current time.
The option argument is a decimal number of the form

[[CC]YY]MMDDhhmm[.SS]

where each two digits represents the following:

CC The first two digits of the year.

YY The second two digits of the year.

MM The month of the year (01-12).


OR some other useful ones are:

1. find /usr -xdev -depth -size +7000 â xdev -exec ll {} \; | more
(finds files larger than 7000k)

2. find /usr -type f -size +1000000c -xdev -exec ls -l {} \;
(if you want to search for a number of characters try the lower case c after the number)
OR


3.find /usr -xdev -size +1000000c -exec ll {} \;
(searches for directories as well as files.)

[Patrick Scherrer]

Thanks Adam.....that at least gave me some more idea's to look. When I search user for really big files, I'm still getting nothing bigger than 10 MB or so.

[Pete Randall · Accepted solution]

Patrick,

I have to wonder if there was a file, now deleted, that the space has not been given back yet. You can use lsof to find such a thing: # lsof +L1

Take a look at this thread:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1129437


Pete

[Patrick Scherrer]

A number of database processes that had been launched as part of a batch were hung up.

lsof helpded me clean up the processes which immediately freed things up.

Thanks

[Patrick Scherrer]

Problem solved thanks!

[Pete Randall]

Patrick,

I would take a long, hard look at those processes. It just doesn't seem right to me that they're writing to /usr - far more appropriate would be /var/tmp or something similar.


Pete