Repository navigation
fix(backup): a sentinel that is another volume's companion is not, on its own, a crossed mapping (#468) - #469
Merged
Merged
Conversation
… its own, a crossed mapping (#468) Since 2026-09-13 backup-volumes and verify-backups have both exited 2, and every loki-data archive on the host — five sets that verified clean on the 12th — failed the same line: "this archive carries the sentinel of paperless-data". #133 gave paperless-data the sentinel ./index; a Loki data volume has a top-level ./index of its own, listed two tables down as a loki-data companion, and the change reached the host with the 2026-09-12 revision. The archives were intact. No manifest was written after 2026-09-06 and nothing was pruned. ./index stays: it is the marker that was measured off a boot of the pinned image, and nothing about Paperless changed. What changes is how verify() reads a foreign sentinel that is one of the volume's own companions. It is now a "soft" hit, counted as foreign only when the volume's own sentinel is absent too — in --hot as well as strict, because an archive that carries paperless-data's marker and lacks loki-data's is exactly the crossed mapping the check exists to catch. A foreign sentinel that is not a companion is fatal as before. load_inventory() additionally refuses a table in which two volumes share a sentinel outright, the case owner[] cannot represent, so that class of edit fails by name before any service is stopped. Verified on fake sets with a stand-in for age: a Loki archive with ./chunks and ./index verifies in strict and hot modes; a Paperless-shaped archive filed as loki-data (./index, no ./chunks) fails in both; a loki-data archive carrying ./grafana.db fails as before; a table with paperless-media set to ./index dies at --inventory. shellcheck clean; check_docs.py passes. Not deployed — converge is report-only, so the host applies it by hand; the next Sunday set is the proof, and the nightly verify the day after. Found from the wiki side by reading the units' journal out of Loki (Gerrrt/Lemmiwinks#279). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Sep 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
scripts/backup-volumes.sh:verify()treats a foreign sentinel that is one of the volume's ownCOMPANIONSas a soft hit — foreign only when the volume's own sentinel is absent too, in--hotas well as strict.load_inventory()gainscheck_sentinel_table(), which refuses a table in which two volumes share a sentinel outright. TheSENTINELcomment records the case;docs/roadmap.mdgains the Done entry.Why
#468. From 2026-09-13 both
backup-volumesandverify-backupsexit 2, and everyloki-dataarchive on the host — five sets that verified clean on the 12th — fails:#133 set
SENTINEL[paperless-data]="./index"; a Loki data volume has a top-level./index, and the same script lists it underCOMPANIONS[loki-data]. The change reached the host with09f2cdc(2026-09-12); the first weekly run after it failed, and every nightly verify since. The archives are intact; no manifest since 2026-09-06../indexstays — it was measured off a boot of the pinned image and nothing about Paperless changed. The check changes instead: a marker this volume is documented to carry cannot, alone, prove the archive belongs to somebody else. It still proves it when the volume's own marker is missing, which is what a mislabelled archive looks like and what a real Loki volume never does.Blast radius
Verification logic only. No service, image, port, rule or credential changes. Existing behaviour is unchanged for every foreign sentinel that is not a companion of the volume under test.
secrets/*.sops.yamlVerification
Fake sets, with a stand-in
ageonPATHthat cats the file (this machine has noage):--hot./chunks,./index,./walloki-data:./index,./log, no./chunksloki-dataarchive carrying./grafana.dbpaperless-mediaalso set to./index--inventory: paperless-data and paperless-media share the sentinel ./indexshellcheck scripts/backup-volumes.shcleanpython3 scripts/check_docs.py— docs OKmake validatein full — not run here (nopromtool/docker on this host); CI runs itFound from the wiki side by reading the units' journal out of Loki (Gerrrt/Lemmiwinks#279).
🤖 Generated with Claude Code