In the ext4 file system, what does an inode mainly store?
Think about what information is needed to manage a file without storing its name or content.
An inode stores metadata about a file, including permissions, ownership, timestamps, and pointers to the file's data blocks. It does not store the file name or the actual content.
Which structure in ext4 points to the actual data blocks of a file?
Consider where the file system stores the location of file content.
The inode holds pointers to the data blocks where the file's actual content is stored. Directory entries only map file names to inode numbers.
Ext4 inodes have direct, single indirect, double indirect, and triple indirect pointers. Why are indirect pointers used?
Think about file size limits and how pointers can extend addressing capacity.
Direct pointers can only address a limited number of blocks. Indirect pointers add layers of referencing, allowing the file system to handle very large files by pointing to blocks that themselves contain pointers.
Which statement correctly describes the relationship between inode numbers and file names in ext4?
Consider how the file system links names to metadata.
In ext4, directory entries hold file names and link them to inode numbers. The inode itself does not contain the file name but stores metadata and pointers to data.
In ext4, if an inode is deleted but the directory entry pointing to it is not removed, what is the likely outcome?
Think about what happens when metadata is missing but references remain.
If the inode is deleted but the directory entry still exists, the directory entry points to a non-existent inode. This causes errors when trying to access the file because the metadata and data pointers are missing.