Next: Registering the File Systems
Up: The Virtual File System
Previous: The VFS Superblock
Like the EXT2 file system, every file, directory and so on in the VFS is represented
by one and only VFS inode.
The information in each VFS inode is built from information in the underlying file system
by file system specific routines.
VFS inodes exist only in the kernel's memory and are kept in the VFS inode cache
so long as they are useful to the system.
Amongst other information, VFS inodes contain the following fields:
- This is the device identifer of the device holding the file or whatever
that this VFS inode represents,
- inode number
- This is the number of the inode and is unique within this file system.
The combination of device and inode number is unique within the Virtual
- Like EXT2 this field describes what this VFS inode represents as well
as access rights to it,
- user ids
- The owner identifiers,
- The creation, modification and write times,
- block size
- The size of block for this file in bytes, for example 1024 bytes,
- inode operations
- A pointer to a block of routine addresses. These routines
are specific to the file system and they perform operations for this inode, for
example, truncate the file that is represented by this inode.
- The number of system components currently using this VFS inode. A count
of zero means that the inode is free to be discarded or reused,
- This field is used to lock the VFS inode, for example, when it is being
read from the file system,
- Has this VFS inode been written to, if so the
underlying file system will need modifying,
- file system specific information
David A. Rusling