Seriously, inodes are an important part of the UNIX filesystem. You don't need to worry about them most of the time, but it does help to know what they are.
An inode is a data structure on the disk that describes a file. It holds most of the important information about the file, including the on-disk address of the file's data blocks (the part of the file that you care about). Each inode has its own identifying number, called an i-number. You really don't care about where a file is physically located on a disk. You usually don't care about the i-number - unless you're trying to to a file. But you do care about the following information, all of which is stored in a file's inode:
The file's ownership: the user and thethat own the file
The file's: whether or not various users and groups are allowed to read, write, or execute the file
The file's: when the file itself was last modified, when the file was last accessed, and when the inode was last modified
The file's type: whether the file is a regular file, a special file, or some other kind of abstractionas a file
Each filesystem has a set number of inodes that are created when the filesystem is first created (usually when the disk is first initialized). This number is therefore the maximum number of files that the filesystem can hold. It cannot be changed without reinitializing the filesystem, which destroys all the data that the filesystem holds. It is possible, though rare, for a filesystem to run out of inodes, just like it is possible to run out of storage space - this can happen on filesystems with many, many small files.