Organise data on disks with directories, inodes and journaling.
File systems organise persistent data in files and directories with metadata, allocation (inodes, extents) and journaling for crash consistency. Examples: ext4, NTFS, APFS, ZFS. Permissions, links, caching and fragmentation affect behaviour; SSDs add wear levelling.
ls -l shows owner, group and permission bits of files.
File systems organise data on disks, and their design determines reliability, speed and how well data survives crashes.
Organise data on disks with directories, inodes and journaling.
File systems organise data on disks, and their design determines reliability, speed and how well data survives crashes.
A structure that stores a file's metadata and the locations of its data blocks, separate from the file name.
Recording intended changes in a log before applying them, so the file system can recover a consistent state after a crash.
Typical applications include recovering a disk after a power cut using a journal, finding how a file's blocks are located through inodes and choosing a file system for a server that stores many small files.
Study "Virtual memory" first (topic 60 of 104 in Software & Computing). It covers the groundwork this topic builds on.
Inodes. Hard vs symbolic links. Journaling.
ls -l shows owner, group and permission bits of files.
The next topic is "Synchronisation primitives", which builds directly on this one.
It is classed as Intermediate in Software & Computing (topic 61 of 104). It is an intermediate topic. Work through the beginner topics in Software & Computing first.
Want to practise? Open the interactive course for quick checks, quizzes, simulations and progress tracking.