Storage, volumes & filesystems¶
From a block device to a mounted filesystem, without a C library anywhere.
| Organisation | Repos | Site | Docs | What it holds |
|---|---|---|---|---|
go-volumes |
9 | site | docs | The block layer — a device contract, NBD, pools, replicas, S3, an OCI image as a block device, GPT and MBR, and parse-hardening guards. |
go-filesystems |
20 | site | docs | Filesystem-format drivers — ext4, xfs, btrfs, zfs, apfs, ntfs, exfat, fat32, iso9660, squashfs and more — plus UEFI variable management and a format prober. And the other direction: NFSv3, SFTP and WebDAV servers that export any of them, so an image can be mounted by the host rather than only read by a program. |
go-diskimages |
6 | site | docs | Disk-image formats: qcow2, raw, dmg, tart-oci, in either direction. |
go-fsctl |
6 | site | docs | Linux kernel ioctl wrappers — zfs, btrfs, loop, device-mapper, block, copy-on-write clones. |
go-fde |
4 | site | docs | Full-disk encryption: LUKS, APFS, and the plumbing that opens them. |
go-encryptions |
3 | site | docs | The modes underneath: CCM, XTS, ZFS crypto. |
Counts are public repositories that hold code; brand, docs and landing repositories are excluded.