Skip to content

test: check multi-node file histories against the documented guarantees - #156

Merged
mattmattox merged 3 commits into
mainfrom
test/coherence-history
Nov 16, 2026
Merged

mattmattox merged 3 commits into
mainfrom
test/coherence-history

Conversation

@mattmattox

Copy link
Copy Markdown
Contributor

A Jepsen-style checker for the cross-node guarantees in the docs. Clients on 2-4 mounts hammer 5 shared names with create, write, read, stat, readdir, unlink and rename, recording every call's start and end on one clock. history.Check then flags what no allowed order explains:

  • stale reads right after open;
  • names, sizes and listings still wrong after -attr-timeout plus slack;
  • resurrected names;
  • torn reads;
  • EEXIST from open(O_CREAT) without O_EXCL;
  • unexpected errors;
  • a rename showing in a listing as both names or neither.

Porcupine wasn't a fit: the guarantees are windowed, not linearizable.

TestCoherenceHistory runs only with GCFS_HISTORY=1, because main fails it today (findings in the PM's notes: cross-file reads, a block leak, EISDIR from open, EEXIST). Fixes come next, each rerun under this checker. The checker's own unit tests always run.

Per the PM, a read split at 4 KB boundaries while a write on the same node overlaps it is allowed, and OPERATIONS.md now says so. Mid-sector tears stay violations.

🤖 Generated with Claude Code

mattmattox and others added 3 commits November 16, 2026 11:04
…ed guarantees

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ing a local write, and track the checker in the manifest

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mattmattox
mattmattox merged commit a5273c1 into main Nov 16, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant