The new company's test machine disk space is very small, log a lot, also very big, do a log compression script, 4:30 in the night automatically run, the second day found disk space is full, had to delete useless logs, empty space, can be weird is how to delete useless files, space or occupy a lot.
With the Du root directory, it is found that these files are not up to the size of space occupied.
I've also met this kind of problem, which is usually restarted, because a bad disk corruption can cause this problem.
or df-i view inode usage, the inode is not enough to cause this problem. Can see the inode is enough.
This time I was a little Niang, "disk space is not released", according to an article dry, resolved the problem.
The records are as follows:
Yesterday to help colleagues fix a disk space is "invisible" occupation of the incurable diseases, summary records for forgetting.
1, with DF Check discovery/root directory free space is 0
[[Email protected]/] #df-H
2, with du inspection found that each directory occupies little space, there is about 3g of space inexplicably lost.
[Email protected]/]# du-m–max-depth=1 |sort-gr
3, with lsof examination only found the reason is that there is a file is deleted, and the process is still alive, resulting in space-occupying phenomenon
[[Email protected]/]# lsof |grep Delete
According to the process number listed by lsof, after kill these processes, the space is released.
Problems with disk free space and space usage