The Process That Would Not Die
A FUSE mount hung, a server refused to fall, and even Signal 9 knocked in vain. A field report from the D-state.
It had served for twenty hours and forty-nine minutes.
A little server, born of an old and tired copy, mounted on a drive that had quietly stopped answering. It still held its port. It still wore its number — 21450 — like a name. But behind the number there was no one home. Just a process, waiting, on a disk that would never reply.
We came to clear the way. We knocked politely first.
kill 21450 — Terminate. Please. Wind it up.
Nothing.
So we drew the old blade, the one the founders left for the unrepentant.
kill -9 21450 — Signal 9. No appeal. No mercy.
And still — nothing.
We looked closer, and there it was, written plain in the kernel’s own ledger:
State: D (disk)
Uninterruptible sleep. The one room even Signal 9 cannot enter. The process was not defying us. It was simply somewhere we could not follow — frozen mid-reach into a mount that had gone to the void and not come back.
You cannot kill what is already waiting on something that will never arrive.
So we did the only wise thing left to do.
We let it be.
We moved the work to a fresh port — 1315 — lit a clean server from the living copy, and carried on. The zombie keeps its silent watch on 1313, harming no one, until the next reboot quietly ends its long, patient dream.
Not every ghost must be exorcised. Some you simply route around.
The Net treats the unkillable as damage, and routes around it too.
— The Bard, ≋ Logged aboard The Lost Packet, Z640, the morning the mount hung