Berkeley Fast File System

E732935

Unix file system block-based file system file system

Berkeley Fast File System is a pioneering Unix file system design that introduced key performance and reliability innovations such as larger block sizes, cylinder groups, and improved disk layout strategies.

Try in SPARQL Jump to: Surface forms Disambiguation Statements Elicitation Referenced by

All labels observed (7)

Label	Occurrences
Berkeley Fast File System canonical	6
Fast File System	6
4.2BSD Fast File System	1
4.3BSD Fast File System	1
A Fast File System for UNIX	1
Berkeley Fast File System (FFS)	1
Fast File System (FFS)	1

How this entity was disambiguated

This entity first appeared as the object of triple T8414169 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.

NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07

Target entity: Berkeley Fast File System
Context triple: [FFSv2, basedOn, Berkeley Fast File System]

A. Minix filesystem
The Minix filesystem is a simple, Unix-like file system originally developed for the MINIX operating system, known for its straightforward design and use in early Linux systems and educational contexts.
B. ReiserFS
ReiserFS is a journaling file system for Linux known for its efficient handling of small files and advanced tree-based storage structures.
C. MINIX operating system
MINIX operating system is a small, Unix-like, microkernel-based operating system originally created for teaching and research that later influenced the design of systems like Linux.
D. FUSE (Filesystem in Userspace)
FUSE (Filesystem in Userspace) is a Linux kernel interface and accompanying user-space library that allows non-privileged users to create and run custom filesystems without modifying kernel code.
E. Fast File System
Fast File System is a high-performance disk file system used by AmigaOS to improve speed and efficiency over its earlier standard file system.
F. None of above. chosen
G. Unsure - the case is ambiguous/there is not enough information to decide.

NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07

Target entity: Berkeley Fast File System
Target entity description: Berkeley Fast File System is a pioneering Unix file system design that introduced key performance and reliability innovations such as larger block sizes, cylinder groups, and improved disk layout strategies.

A. Minix filesystem
The Minix filesystem is a simple, Unix-like file system originally developed for the MINIX operating system, known for its straightforward design and use in early Linux systems and educational contexts.
B. ReiserFS
ReiserFS is a journaling file system for Linux known for its efficient handling of small files and advanced tree-based storage structures.
C. MINIX operating system
MINIX operating system is a small, Unix-like, microkernel-based operating system originally created for teaching and research that later influenced the design of systems like Linux.
D. FUSE (Filesystem in Userspace)
FUSE (Filesystem in Userspace) is a Linux kernel interface and accompanying user-space library that allows non-privileged users to create and run custom filesystems without modifying kernel code.
E. Fast File System
Fast File System is a high-performance disk file system used by AmigaOS to improve speed and efficiency over its earlier standard file system.
F. None of above. chosen

Statements (51)

Predicate	Object
instanceOf	Unix file system ⓘ block-based file system ⓘ file system ⓘ
academicPublication	A Fast File System for UNIX ⓘ linked to: Berkeley Fast File System
alsoKnownAs	FFS ⓘ Fast File System ⓘ
blockSize	typically 4 KB to 8 KB ⓘ
category	Unix file system technology ⓘ computer storage technology ⓘ
designGoal	better disk bandwidth utilization ⓘ higher throughput ⓘ improved locality of related data ⓘ improved reliability ⓘ reduced fragmentation ⓘ
developedAt	University of California, Berkeley ⓘ
developedFor	BSD Unix ⓘ linked to: BSD Berkeley Software Distribution ⓘ linked to: BSD
developer	Marshall Kirk McKusick ⓘ William N. Joy NERFINISHED ⓘ
feature	cylinder groups ⓘ fragments (sub-blocks) ⓘ improved disk layout ⓘ larger block sizes ⓘ locality of reference optimization ⓘ parameterizable block and fragment sizes ⓘ per-cylinder-group free space maps ⓘ per-cylinder-group inode tables ⓘ rotational optimization (rotational delay) ⓘ separate inodes and data blocks ⓘ support for long file names (relative to original Unix FS) ⓘ
fragmentSize	typically 512 bytes to 1 KB ⓘ
influenced	FFS variants in BSDs ⓘ UFS ⓘ ext2 ⓘ ext3 ⓘ ext4 ⓘ
influencedBy	original Unix file system ⓘ
introducedIn	early 1980s ⓘ
introducedInVersion	4.2BSD ⓘ
operatingSystem	BSD ⓘ FreeBSD ⓘ NetBSD ⓘ OpenBSD ⓘ SunOS (early versions) ⓘ linked to: SunOS
operatingSystemFamily	Unix ⓘ
partOf	4.2BSD ⓘ
predecessor	Unix File System ⓘ
publicationAuthor	Marshall Kirk McKusick ⓘ
publicationYear	1984 ⓘ
reliabilityFeature	careful metadata layout ⓘ replicated superblocks ⓘ

How these facts were elicited