Storage, volumes & filesystems
Storage, volumes & filesystems
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 | 34 | site | docs | One Filesystem interface, and everything that can sit on either side of it. Underneath, the formats: ext4, xfs, btrfs, zfs, apfs, ntfs, exfat, fat32, ffs, ufs, hfsplus, iso9660, squashfs, UEFI variables, a blkid-style prober — and archives read as filesystems rather than unpacked, cab, cpio, rar, rpm, 7z (which also writes), xar and WARC, with one extractor that sniffs the format from the bytes and follows multi-volume sets. Above it, the servers that export any of them — NFSv3, SMB2, SFTP, WebDAV and an S3 object API — so an image is mounted by the host instead of only read by a program. And between the two: a host directory confined with os.Root, a read-only filesystem made writable through a spool, and the same filesystem served across a connection. |
go-diskimages | 6 | site | docs | Disk-image formats: qcow2, raw, dmg, tart-oci, in either direction. |
go-fileshare | 4 | site | docs | The product go-filesystems’ servers make possible: one configuration and one binary sharing a disk image over SMB, NFS, WebDAV and SFTP, with an OIDC portal, per-server tokens, a file explorer and an admin console across many servers. |
go-fsctl | 7 | 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 | 4 | site | docs | The modes underneath: CCM, XTS, ZFS crypto. |
Counts are public repositories that hold code; brand, docs and landing repositories are excluded.