This is a research paper I wrote about inodes for my Linux class at the University of Advancing Technology.
Whenever a new file is created, inodes, also called index nodes, are created with the file. Inodes for each file do not consist of the actual date inside the file, but instead, they contain the extra information about the file. This extra information is referred to as “metadata”, or “data about data”.
While files can be very large, the inode of even a large file can still be quite small. Inodes of files in a file system only take up, “roughly of 1% of the total disk space, whether it is a whole storage unit (hard disk, thumb drive, etc.) or a partition on a storage unit” (Buse). I think this is why the common computer user hasn’t heard of an inode before—it takes up so little space, that they don’t notice them. However, a user has seen parts of an inode of a file before, probably without realizing it. This is because inodes can consist of many different pieces of information about the file, as was said before.
Inodes can specifically contain changes made to the data in the file, and who changed that certain information, as well as when it occurred, and how much data the file now has. Inodes can potentially also contain data about the owner of the file, and permissions to other users granted by the owner, and status flags about the data in the file. The structure of an inode is actually a bit like building blocks, each containing some part of the metadata listed above. For each piece of information, there’s a default block size for it to be contained in, but this only occurs “[w]henever a partition is formatted with a file system” (Pillai).
Inodes, besides holding the metadata, are very useful too. Using the terminal, users are able to type in commands using inodes to find or even delete a file. Users can also change directories using it inode number.
There is limited space in the inode structure and “can be filled before the data portion of the storage unit” (Buse). However, this may only be the case of there are many smaller files within a structure until the inode storage is freed within it.
Users can also check inode utilization by typing specified commands into the terminal. Users are able to find out how many more inodes can be created within the storage unit, and what each inode for files consists of, depending on the type of file and how large the file is.
Works Cited
Buser, Jarret W. “Intro to Inodes.” Linux.org. N.p., 9 July 2013. Web. 23 Sept. 2014. <http://www.linux.org/threads/intro-to-inodes.4130/>.
Pillai, Sarath. “Inode and Its Structure in Linux.” [/ROOT.IN~]#:. Hello Bar, 1 Dec. 2012. Web. 23 Sept. 2014. <http%3A%2F%2Fwww.slashroot.in%2Finode-and-its-structure-linux>.