bugs/OSX: Assistant leaves repo in inconsistent stategit-annexhttp://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/git-annexikiwiki2016-03-12T16:58:09Zgit annex repair --forcehttp://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/comment_1_0dfd9eedccb48f1f3d7939677dc96446/Marco2016-03-12T16:58:09Z2015-05-15T08:01:25Z
<p>This command removed all history. It looks like no file was ever added.</p>
<p>Any idea how I should handle this client repository? I could clone again from a backup. Is it possible to keep the annex UUID for a new clone?</p>
Disaster recoveryhttp://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/comment_2_5c5e7356cae8ddf8d2c8964fb69000f5/Marco2016-03-12T16:58:09Z2015-05-15T09:40:16Z
<p>Ah, found it:</p>
<p>https://git-annex.branchable.com/design/assistant/disaster_recovery/</p>
<blockquote><p>As long as the git repository has at least one remote, another method is to clone the remote, sync from all other remotes, move over .git/config and .git/annex/objects, and tar up the old broken git repo and git annex add it</p></blockquote>
A possible solutionhttp://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/comment_3_1e0841d71c33fd3919310f1711b6e0b4/Marco2016-03-12T16:58:09Z2015-05-19T11:03:22Z
<p>While searching for the problem I found this:</p>
<p>http://feeding.cloud.geek.nz/posts/error-while-running-git-gc/</p>
<blockquote><p>git reflog expire --all --stale-fix</p></blockquote>
<p>I can't verify this because I nuked the broken repository after recreating it.</p>
Once againhttp://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/comment_4_eb5b0f8259d861000510fcfd58f66617/Marco2016-03-12T16:58:09Z2015-06-08T15:45:15Z
<p>I was using the assistant on two machines in parallel and both git repositories got broken. Before that I was just using the command line tools and just one assistant. Today the history got inconsistent when firing up the second assistant.</p>
<p>Repos in use:
- client 1 with active assistant
- client 2 with active assistant
- Synology NAS with git-annex installed (armel-based)</p>
<p>I could recover everything pretty fast by cloning again from the nas device. Copying the .git/config and moving over the .git/annex directory.</p>
<p>I will send you the log-files via mail.</p>
How to debug?http://git-annex.branchable.com/bugs/OSX__58___Assistant_leaves_repo_in_inconsistent_state/comment_5_4343ee35e4091fc50268f9fc611f5148/Marco2016-03-12T16:58:09Z2015-07-25T18:10:08Z
<p>I want to give the two assistants one more try with the newest version.</p>
<p>But I want the assistant not to try a repair once a failure is detected. I want to check the state of the repository to get a clue what goes wrong.
As I understood the code there is no configuration to prevent the repair. Am I wrong? If not I could try to introduce one if it makes sense.</p>