file allocation table
Data & Storage

Meaning

A File Allocation Table (FAT) is a data structure used by many file systems to map each file to the list of disk clusters that store its contents. It solves the problem of locating file data quickly without scanning the whole disk, which is essential for performance on low‑resource storage. The FAT is consulted whenever the operating system needs to read, write, or extend a file, translating logical file offsets into physical block addresses.

Primary Function

File system metadata

Communicative Purpose

Enables rapid lookup of file locations on disk

Pattern

collect file metadata → build FAT entries → map logical file names to physical clusters

Core Structure

cluster = FAT[entry]

Função primária

File system metadata

Propósito comunicativo

Enables rapid lookup of file locations on disk

Situações de gatilho

Operating systems: locating file blocks during read/write Embedded devices: managing limited storage space without fragmentation

Contextos

Operating system kernels, file system drivers, storage management utilities

Padrão

collect file metadata → build FAT entries → map logical file names to physical clusters

Estrutura central

cluster = FAT[entry]

Colocados típicos

  • directory entry
  • cluster chain
  • boot sector
  • root directory

Substituições comuns

  • Using NTFS MFT instead of FAT – provides richer metadata but more complexity
  • Using exFAT – supports larger files but less compatibility

Erros comuns

Assuming FAT entries are always contiguous – leads to fragmented reads; Ignoring reserved clusters – can cause filesystem corruption; Overlooking end‑of‑chain marker – results in infinite loops when traversing clusters

Similar / contraste

NTFS Master File Table – stores per‑file metadata in fixed records; ext2 inode table – uses fixed‑size inodes rather than a cluster chain

Interferências

Coming from Linux ext4: assuming journaling – FAT lacks journaling, so unexpected power loss can corrupt the table

Família do chunk

  • inode table
  • directory entry
  • cluster chain
  • boot sector

Nuance

1) Do not use FAT for large modern disks where fragmentation overhead is high. 2) FAT lookup is O(1) but traversing long cluster chains can be slower than indexed inode lookups. 3) FAT cannot store extended attributes; attempting to store them leads to data loss.

Efeito pragmático

Correct use of FAT enables reliable file access on simple storage media and reduces implementation complexity for embedded systems.

Dica de memória

Think of the FAT as a city map where each street sign (cluster) points to the next block of a road leading to the destination (file data).

Nota

FAT stores cluster numbers as 12‑, 16‑, or 32‑bit values; the size determines the maximum addressable volume.

Upgrade path

Transition to NTFS or exFAT for advanced features such as journaling and larger file support

Frequência: HighFormulaicidade: FixedTipo de construção: conceptPrioridade de aquisição: Recognition firstPrioridade de output: BothTag de espaçamento: Medium-term

Log in to save chunks.