FreeBSD's VFS Layer: How Multiple Filesystems Share One Interface
How the Virtual File System abstraction lets FreeBSD run UFS, ZFS, tmpfs, and NFS behind the exact same open()/read()/write() calls, and what that abstraction actually costs.
tag
8 posts
How the Virtual File System abstraction lets FreeBSD run UFS, ZFS, tmpfs, and NFS behind the exact same open()/read()/write() calls, and what that abstraction actually costs.
Using bind mounts to expose the same directory at multiple paths, and OverlayFS to layer a writable surface on top of read-only content — the two mechanisms containers are built on, directly usable on their own.
How the File Allocation Table represents files as linked chains of clusters, and why that simple design has both strengths and hard limits.
How ZFS's storage pools, datasets, and copy-on-write snapshots fit together on FreeBSD, with the commands you'll actually use day to day.
df says you have plenty of free space, but every write fails with ENOSPC. Two completely different root causes look identical from the outside — here's how to tell them apart.
How the VFS layer lets ext4, XFS, Btrfs, NFS, and procfs all answer to the same read/write/open calls.
How APFS's container/volume model, copy-on-write clones, and snapshots replaced HFS+ across every Apple platform.
How NTFS's Master File Table, transaction journal, and lesser-known features like alternate data streams actually work.