What is happening
Mercurial documents dirstate reconstruction separately from revlog recovery. Known-good clones can supply missing history, while lossy conversion may change revision hashes and require every user to re-clone.
Mercurial repository recovery
Mercurial separates working-directory state from repository history under .hg. Damage to dirstate can confuse local status, while missing or corrupt revlogs in .hg/store can remove changesets, manifests, or file revisions.
Understand the symptom
Mercurial documents dirstate reconstruction separately from revlog recovery. Known-good clones can supply missing history, while lossy conversion may change revision hashes and require every user to re-clone.
What you may see
A changeset, manifest, or file revision cannot be located.
Working-directory parent pointers are invalid.
Repository history is unreadable at a specific point.
Current content survived while dirstate or metadata did not.
Protect the source
It may restore parent state without reconstructing every local intent.
Branches, tags, integrations, and clones may need reconciliation.
A supposedly separate copy may reference the same underlying storage.
Do this now
Keep .hg and uncommitted files together with permissions and timestamps.
Record the first error, affected revlog, repository requirements, and version.
Preserve remotes, bundles, CI checkouts, developer clones, and release artifacts.
Identify modified, added, removed, ignored, and untracked files before rebuilding state.
NEPFOSYS process
NEPFOSYS maps requirements, changesets, manifests, revlogs, dirstate, bookmarks, phases, and readable ranges.
Clones, bundles, working files, and intact revlogs are correlated on protected copies.
hg verify, revision graphs, tags, branches, file histories, hashes, and working changes are reviewed.
A clear next step
Start a case with the exact symptoms, incident timeline, prior attempts, encryption details, and the files that matter most. NEPFOSYS will route the case to the appropriate DFW intake or nationwide mail-in path.
Start with a case reviewQuestions, answered
No. Dirstate tracks the working copy; revlogs store repository history.
Often it can supply missing history if it contains the same revisions and repository format.
Not necessarily; lossy recovery can create a new history that requires re-cloning.
DFW local · Nationwide mail-in