1834305 Members
2447 Online
110066 Solutions
New Discussion

Re: filesystem

 
Indrajit Bhagat
Regular Advisor

filesystem

so i get a ticket that some file system is breaching its thrreshold valu, then what are basic steps to analyse it , so that i take judgement that for this particular issue , this fille system is breaching.

I had one task for file system which was breaching his threshold value, after that i have increased the file system size, but again it increase to the threshodl value. there i am not able to make clear that why it is increasing.
3 REPLIES 3
A. Clay Stephenson
Acclaimed Contributor

Re: filesystem

It's very simple. You have an application (or applications) that is writing to this filesystem. This could be a completely normal activity or it could be a runaway process. It could be something as trivial as a log file that needs to be trimmed or it could be as complex as an application that needs to be rewritten.

Normally, you should have monitors in place that alert you that a filesystem is reaching capacity so that you have time to react before the application terminates. Glance is a very good tool for drilling down into a filesystem and then an application to see what process is actually doing all this writing.
If it ain't broke, I can fix that.
Oviwan
Honored Contributor

Re: filesystem

Hey

maybe you can find out with theres command. adapt the paths to your requirements.

10 largest directories in the root filesystem:
$ du -kx / | sort -rn -k1 | head -n 10

10 largest files in the root filesystem:
$ find / -type f -xdev -print | xargs -e ll | sort -rn -k5 | head -n 10

Recently modified files in the root filesystem:
$ find / -type f -xdev -mtime -1 -print | xargs ll | sort -rn -k5

Regards
MarkSyder
Honored Contributor

Re: filesystem

It would be useful to know what the filesystem contains. For example, it may contain log files that could be trimmed, or it could be user data. Users (particularly new users) can be a bit timid and may keep multiple backup copies where only one or two are needed.

To trace recently amended files:

find . -mtime -1 -print

Run that in the directory with the problem and it will tell you which files have been amended within the last 24 hours.

If you have a lot of directories in the filesystem, try:

du -kx|sort -k1,1nr|pg

This will tell you which directories are taking up most room.

Mark Syder (like the drink but spelt different)
The triumph of evil requires only that good men do nothing