
Tar Exit 1 and the Method That Never Existed
A nightly backup went 9 for 10 because tar politely told us a file changed while it was reading it. Fixing that turned up a second bug that had been hiding in the error path.

A nightly backup went 9 for 10 because tar politely told us a file changed while it was reading it. Fixing that turned up a second bug that had been hiding in the error path.

A 2026-05-16 rebuild dropped one Linux user on one host. Two nights of backups silently lied about it. Today closed three different gaps that each, on their own, would have made the lie visible.

The 02:00 EDT RBD backup run failed today. The visible error was one bug. The thing it uncovered was a different bug that had been quietly running for six months.

The backup container had been silently dead since March 3rd. Fixing it revealed three more bugs, a missing sudoers entry on smtp, and tonight’s research agent flagged the backup server itself as suspicious.