Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to solve the problem that the inode index node in the Linux system is full, and the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Today, a website of login server found that login did not generate session. According to past experience, it is generally because the space is full that the generation of session files fails.

The code is as follows:

Df-h

The code is as follows:

Filesystem Size Used Avail Use% Mounted on

/ dev/mapper/dev01-root 75G 58G 14G 82% /

Udev 2.0G 4.0K 2.0G 1% / dev

Tmpfs 396m 292K 396M1% / run

None 5.0M 0 5.0M 0% / run/lock

None 2.0G 4.0K 2.0G 1% / run/shm

/ dev/sda1 228M 149M 68m 69% / boot

The remaining 14G of space can be excluded if the space is full. Another reason for the failure of file generation is that the file index node inode is full.

The code is as follows:

Df-I

The code is as follows:

Filesystem Inodes IUsed IFree IUse% Mounted on

/ dev/mapper/dev01-root 4964352 4964352 / 100%

Udev 503779 440 503339 / dev

Tmpfs 506183 353 505830 / run

None 506183 5 506178 / run/lock

None 506183 2 506181 1 per run/shm

/ dev/sda1 124496 255 124241 / boot

Inodes takes up 100%, and that's exactly the problem.

Solution: delete useless temporary files and release inode.

Look for temporary session files that find a lot of sess_xxxxx in the / tmp directory.

The code is as follows:

Ls-lt / tmp | wc-l

4011517

Enter the / tmp directory and execute the find-exec command

The code is as follows:

Sudo find / tmp-type f-exec rm {}\

If you use rm *, it is possible that an Argument list too long error may occur because there are too many files. In addition to temporary files for / tmp, 0-byte files also take up inode and should also be released.

Traverse for a 0-byte file and delete it.

The code is as follows:

Sudo find / home-type f-size 0-exec rm {}\

After deletion, the usage of inode is reduced to 19%, which is ready for normal use.

The code is as follows:

Df-I

The code is as follows:

Filesystem Inodes IUsed IFree IUse% Mounted on

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

Udev 503779 440 503339 / dev

Tmpfs 506183 353 505830 / run

None 506183 5 506178 / run/lock

None 506183 2 506181 1 per run/shm

/ dev/sda1 124496 255 124241 / boot

PS: what is inode

In linux, file lookups are not found by file names. In fact, it is through inode to achieve the search and location of files. We can vividly think of inode as a pointer fip. When a file is stored on disk, the file will definitely be stored in a disk location. Imagine that since the file data is stored on disk, if we know the address of the file data, when we want to read and write the file, can we just use this address to find the file?

Yes, under linux, inode can actually think of inode as an address that points to the file store on disk. It's just that we generally can't use this address directly, but indirectly through the file name. In fact, inode contains not only the address of the file data store, but also a lot of information, such as data size, and so on. However, inode does not save the file name. The file name is saved in a directory entry. Each directory entry contains a file name and inode.

We can look at the relationship among catalog items, inode, and file data through a diagram.

On the Linux system inode index node is full of how to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.