This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| File Allocation Table | |
|---|---|
| Name | File Allocation Table |
| Purpose | Disk file system allocation table |
| Introduced | 1977 |
| Developer | Microsoft, IBM, Digital Research |
| Implemented in | DOS, Windows, MSX-DOS, CP/M derivatives, DR-DOS |
| License | Proprietary, various |
File Allocation Table
The File Allocation Table is a legacy disk file system indexing scheme used to map file storage on block devices. It underpins many historical and embedded operating system implementations and influenced later designs in Microsoft Windows, CP/M, MS-DOS, IBM PC compatibles, and DOS-compatible ecosystems. The scheme balances simplicity, portability, and low implementation cost, leading to widespread adoption across personal computer and embedded system markets.
Originally introduced to support early microcomputer storage media, the allocation table records cluster chains for each file and manages free space and special markers for end-of-file and bad sectors. The design interacts with FAT12, FAT16, FAT32 variants that trade cluster size, maximum volume size, and metadata overhead. Implementations appear in Microsoft products, IBM PC DOS, and third-party systems like DR-DOS and FreeDOS, and the format remains common on removable media used by vendors such as SanDisk, Kingston Technology, and Seagate Technology.
Development traces to early storage controllers for the IBM Personal Computer era and work at Microsoft and Digital Research during the late 1970s and early 1980s. The table evolved through iterations aligned with MS-DOS releases and the needs of larger media introduced with products from Compaq, Toshiba, and Western Digital. Notable milestones include formalization during the IBM PC launch, extensions for larger disks driven by Windows 95, and ongoing adjustments to support removable media promoted by companies like Sony (Memory Stick) and standards bodies like the SD Association.
Variants of the scheme address addressing width and volume size: 12-bit indexing for early floppy-based systems common in MSX-DOS and early PC-compatible machines; 16-bit for mainstream MS-DOS and Windows NT era support; and 32-bit (often called FAT32) to scale to multi-gigabyte media used by Windows 95 OSR2, Microsoft Windows 98, and later devices. Each variant prescribes boot sectors influenced by Master Boot Record conventions, reserved sectors mirroring patterns used by IBM PC DOS boot loaders, and root-directory handling impacted by designs from Digital Research and Novell.
On-disk layout includes a boot sector with BIOS Parameter Block elements patterned after IBM PC boot flows, a reserved region for the allocation table copies, and data region clusters similar to structures used by CP/M file allocation concepts. The FAT itself is a linear table of cluster entry values; implementations use special entry codes for end-of-file, bad clusters, and reserved markers comparable to control codes in Intel firmware contexts. Directory entries store short filename and attribute bytes, with long filename techniques later introduced via structures resembling VFAT extensions that coexisted with legacy entries used by MS-DOS utilities.
Performance characteristics depend on cluster size, caching strategies implemented in Microsoft Windows kernel drivers, and underlying disk controller behavior found in hardware from Western Digital, Adaptec, and Marvell Technology. Limitations include fragmentation leading to seek amplification on magnetic disks produced by Seagate Technology and Maxtor, scalability ceilings imposed by 12/16-bit index widths, and weak metadata resilience compared to designs like New Technology File System and exFAT. Reliability issues historically prompted tools from Symantec (Norton Utilities), Microsoft (Scandisk), and independent projects like SpinRite to recover and repair damaged tables.
Support spans many storied operating system families: native in MS-DOS, broad in Microsoft Windows through Windows XP and later with drivers, and implemented in open-source systems such as Linux via kernel modules and userspace utilities. Embedded platforms from Palm, Inc., Nokia, and manufacturers in the mobile phone supply chain used FAT variants for flash storage. File system libraries and drivers are provided by projects like NTFS-3G complements, vendor SDKs from Microsoft Corporation, and cross-platform tools maintained by communities around GNU Project and The Linux Foundation.
The format’s ubiquity drove cross-platform interoperability among Apple Inc. devices (via optional drivers), Android distributions, and firmware in cameras by Canon, Nikon, and Sony. Tooling includes filesystem checkers and defragmenters from Microsoft and third parties such as Piriform (Defraggler), recovery suites from Ontrack and Kroll Ontrack, and mount utilities in GNU/Linux distributions. Standards and vendor ecosystems like the SD Association, USB Implementers Forum, and JEDEC reference implementations ensured consistent behavior across media from manufacturers including SanDisk, Toshiba Corporation, Western Digital, and Samsung Electronics.
Category:File systems