Linux inode full workaround

Today, a login server Web site found that login did not generate a session. Based on past experience, the session file generation failure is generally caused by a full space

650) this.width=650; "Src=" Https://s1.51cto.com/oss/201710/31/3a3089af898212da06a670d5aeee52a0.png-wh_500x0-wm_3 -wmp_4-s_1899893560.png "title=" Qq20171031103046.png "alt=" 3a3089af898212da06a670d5aeee52a0.png-wh_ "/>

Space remaining 473M, you can exclude the situation is full of space. Another reason for file generation failure is that the File index node inode is full

2. Df-i

6. Filesystem inodes iused IFree iuse% mounted on

8. /dev/mapper/dev01-root 4964352 4964352 0 100%/

10. Udev 503779 503339 1%/dev

12. Tmpfs 506183 353 505830 1%/run

14. None 506183 5 506178 1%/run/lock

16. None 506183 2 506181 1%/RUN/SHM

18. /DEV/SDA1 124496 255 124241 1%/boot

Inodes occupies 100%, which is really the problem

Workaround: Delete the unused temporary files and release the Inode.

Find a session temp file that has many sess_xxxxx in the/tmp directory

1. ls-lt/tmp | Wc-l

2. 4011517

Enter/tmp directory, execute find-exec command

Find/home-type f-exec rm {} \;

If you use RM *, it is possible that the argument list too long error occurs because of too many files. The reason is that under Linux, trying to pass too many parameters to a system command (LS *; CP *; RM *; cat *; etc..) , a Argument list too long error occurs.

In addition to the TEMP. tmp file, the 0-byte file will also occupy the inode and should be freed.

Traverse looking for 0 bytes of file and delete

Find/home-type f-size 0-exec rm {} \;

After deletion, the inode usage is reduced to 19% and can be used normally.

2. Df-i

6. Filesystem inodes iused IFree iuse% mounted on

8. /dev/mapper/dev01-root 4964352 940835 4023517 19%/

10. Udev 503779 503339 1%/dev

12. Tmpfs 506183 353 505830 1%/run

14. None 506183 5 506178 1%/run/lock

16. None 506183 2 506181 1%/RUN/SHM

18. /DEV/SDA1 124496 255 124241 1%/boot

Linux inode full workaround