Birmingham mumbai

[
 192 
]
This number is usually extremely high and the limit is very hard to reach, though. In 
the case of servers that are used for workloads that can result in your organization 
storing hundreds of thousands of files, the inode limit can become a real problem. I'll 
show you some output from one of my servers to help illustrate this:
df -i 
The output of this command is as follows:
Figure 8.2: Output from the df -i command
As you can see, the 
-i
 option of 
df
 gives us information regarding inodes instead of 
the actual space used. In this 
example, the root filesystem on the example server has a 
total of 
6291456
 inodes available, of which 
74361
 are used and 
6217095
 are free. If you 
have a system that's reporting a full disk (though you see plenty of space is free when 
running 
df -h
), it may actually be an issue with your volume running out of inodes. 
In this case, the problem would not be the size of the files on your disk, but rather the 
sheer number of files you're storing. In my experience, I've seen this happen because 
of mail servers becoming bound (millions of stuck emails, with each email being a file), 
as well as unmaintained log directories. It may seem as though having to contend with 
an inode limitation is unbecoming of a legendary platform such as Linux, however, 
as I mentioned earlier, this limit is very hard to reach unless something is very, very 
wrong. So in summary, in a situation where you're getting an error message that no 
space is available and you have plenty of space, check the inodes.