What if the Linux inode is exhausted?
This article shows you how to run out of Linux inode, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.
There is no problem with uploading files in the background of the website, but suddenly it cannot be uploaded. And there is no error prompt. View disk space usage:
[root@srv-jigocity-web1 iplocate] # df-m
/ dev/mapper/datavg-www
6048 3594 2147 63% / var/www
The website directory has been used 63%, and there are still many unused, so it is not a problem of disk space.
View the file Inode status:
[root@srv-jigocity-web1 helpers] # df-I
Filesystem Inodes IUsed IFree IUse% Mounted on
/ dev/mapper/datavg-www
786432 786432 0 100% / var/www
There is no free inode available, so a new file cannot be created.
The reason is caused by a large number of small cache files. For example, the cache file that records the user's GEO information will continue to grow rapidly and deplete the Inode resources with the growth of user visits.
Therefore, in the design, we should try our best to avoid producing a large number of trivial small files, and a large number of very small files should be put into the database for management. And clean up the temporary documents in time.
The above is what to do when Linux inode is exhausted. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.
