The server name is no longer a server
How SMB.next turns the stock SMB client already installed on Windows, macOS and Linux into the front end of a distributed storage fabric.
Read the damage reportStorage systems / failure engineering / unwanted operating systems
Notes from the awkward bit between “it booted” and “we can prove it is safe.”
Latest field notes
How SMB.next turns the stock SMB client already installed on Windows, macOS and Linux into the front end of a distributed storage fabric.
Read the damage reportA ZFS recovery import exposed why st_dev and mount IDs are observations of the current mount topology, not durable filesystem identity.
Read the damage reportWhy a Linux PID 1 service manager cannot compress intent, process ownership, readiness, health, recovery and runtime generation into one lifecycle enum.
Read the damage reportWhy node-local boot success and a fleet health verdict must remain separate facts.
Read the damage reportSix crash boundaries on real ZFS exposed a recovery loop that could never terminate.
Read the damage reportA correct solver and a correct reconciler combined to delete an operating system and print applied 0 files.
Read the damage reportA ZFS pool needed to move six metres. The standard answer was Ceph. That was a much larger answer than the problem required.
Read the damage reportFour deliberately pathetic actuator verbs replace arbitrary maintainer code.
Read the damage reportWhy a dependency solver that can refuse a request also owes the operator a reason.
Read the damage reportThe number was magnificent, impossible, and almost published. Then the benchmark consumed what the parser actually produced.
Read the damage reportThe RFC sat in a folder until waiting became more irritating than implementing SMB. Then DataTicket happened because why not.
Read the damage reportOngoing series Building a bloody OS From constraint solver to recovery contract → SMB.next track Keep the clients.“Yes, I realise how this looks. Here is the proof that I have not completely lost my mind.”