From 3486a4d370126354a51d424d0b1d33d39611c7d5 Mon Sep 17 00:00:00 2001 From: "arnaud@c1d1cc612a3921dc06a417301be08a3e125478c4" Date: Sat, 23 Jul 2022 15:24:06 +0000 Subject: [PATCH] --- ...l__58___export-tree_object_is_unavailable.mdwn | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/fatal__58___export-tree_object_is_unavailable.mdwn diff --git a/doc/forum/fatal__58___export-tree_object_is_unavailable.mdwn b/doc/forum/fatal__58___export-tree_object_is_unavailable.mdwn new file mode 100644 index 0000000000..cacfb23dcf --- /dev/null +++ b/doc/forum/fatal__58___export-tree_object_is_unavailable.mdwn @@ -0,0 +1,15 @@ +Hello ! + +I'm having a little issue with one of my annexes. Not sure how I got to this point, I might have reset the master branch in one of the repositories to undo changes at some point. + +``` +❯ git annex sync +(merging origin/synced/git-annex into git-annex...) +(recording state in git...) +fatal: entry 'export.tree' object 92ab3e13460c6c7a6e9f19484d1808f22eab0077 is unavailable +git-annex: fd:17: hClose: resource vanished (Broken pipe) +``` + +There is indeed an entry in git-annex:export.log with that checksum. I don't really care about the export, since its to a remote I don't use anymore. But I'm not sure how to make my annex usable again. Marking the remote as dead does not help. I've considered editing all the git-annex:export.log in all the repositories to remove the offending line, but that's quite some work and I'm not sure if that's enough or if I might do more damage. + +Any ideas ?