Differences between version 12 and previous revision of Inode.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 12 | Last edited on Monday, June 4, 2007 2:01:36 pm | by BenStaz | Revert |
| Older page: | version 11 | Last edited on Monday, June 4, 2007 1:45:49 pm | by BenStaz | Revert |
@@ -1,5 +1,7 @@
An inode stores basic information about a regular file, directory, or other file system object. It contains a list of direct, indirect, and doubly and triply indirect pointers. On some FileSystems, very small files can be stored directly in the [Inode] itself.
+
+The inode number is a unique integer assigned to the device upon which it is stored. All files are hard links to inodes. Whenever a program refers to a file by name, the system conceptually uses the filename to search for the corresponding inode.
Sophisticated FileSystems create [Inode]s on demand, but with most, the number of [Inode]s on a [Partition] has to be decided on during FileSystem creation. It is rare to run out of [Inode]s unless you have an unusual usage profile such as storing a news spool or [Squid] cache. Exhaustion of the inodes will prohibit the creation of additional files even if sufficient HDD space exists.
!!How many Inodes do I have free?
