Storage systems5 field notes

Storage work where the configuration is part of the result.

These notes cover local devices, fabrics and object storage. They record the workload, device identity, network assumptions, destructive boundaries and checks needed to understand what a performance or configuration result means.

Storage archive

Choose the problem you are trying to solve

Start with device formatting, a kernel or SPDK target, or an S3 download workload. Each article states what was tested and where the example stops being a safe assumption.

See the automatic storage index
hardware / local-ai / storage

GMKtec EVO-X3: the hardware, BIOS and NVMe baseline

A product-led examination of my Linux-based GMKtec EVO-X3: Strix Halo hardware, its provable firmware state and measured NVMe performance.

storage / benchmarking / s3 / aws

S3 benchmarking with parallel ranged downloads

Benchmark parallel S3 ranged-download performance with s3bench, a Go tool for measuring throughput against AWS S3 and compatible object stores.

storage / spdk / nvme

SPDK NVMe-oF target setup on Ubuntu with RDMA

Build SPDK v26.05 and configure an NVMe over Fabrics target on Ubuntu with RDMA, explicit host access and a persistent JSON configuration.

storage / nvme / linux

NVMe-oF with RoCE Configuration Guide - Ubuntu Server

Configure a persistent Linux NVMe over Fabrics target with RoCE, stable device identities, host access control and explicit network prerequisites.

storage / nvme

Changing an NVMe LBA format safely on Linux

A safety-first guide to inspecting and changing a supported NVMe LBA format, with separate notes on namespace management and secure erase.

02

Commands and primary sources

Use the command reference for a bounded example and the resource directory when the original specification matters.