inode

A file's inode number can be found using the command.

Hard links are represented as different names with the same inode number.

A link count telling how many hard links point to the inode.

In the reiser4 file system, 42 is the inode number of the root directory.

Their data is a location key, or the key of the inode item it points to.

At mount time, the file system driver must read the entire inode chain and then keep it in memory.

Every file or directory is represented by an inode.

Hard links are implemented by storing the same inode number with more than one file name.

Each inode on the filesystem has two glocks associated with it.

Usually the iNode is set to 128 bits to avoid compatibility issues with some servers.

In ext4 unallocated block groups and sections of the inode table are marked as such.

This is unlike symbolic links, which depend on the original name, not the inode (number).

The indirect block, inode and directory formats are almost identical.

There can be four extents stored in the inode.

For example, a 12-block file would be described using just the inode because its blocks fit into the number of direct pointers available.

Accessing the file by either name results in the same inode number, and therefore the same data.

Starts watching the inode pointed to by pathname for events contained in mask.

Because of their small size, icons can be stored within inode of files.

Installation of new libraries is simple with inode filesystems.

' is a Unix system call that returns file attributes about an inode.

The special inode number 0 represents an unlink.

The file still has the same inode.

In UN mode, the inode must not cache any metadata.

Systems with fast symlinks often fall back to using the original method if the target path exceeds the available inode space.

All file metadata is kept in the inode.