forum/Git annex 'corrupting' itselfgit-annexhttp://git-annex.branchable.com/forum/Git_annex___39__corrupting__39___itself/git-annexikiwiki2014-01-13T20:47:18ZJust happened for me as well.http://git-annex.branchable.com/forum/Git_annex___39__corrupting__39___itself/comment_1_bcf50a215e2f8771e098aadfff4c300c/Jonas2013-11-27T22:47:37Z2013-11-12T08:10:56Z
<p>This was the first search result when I googled the error message, I'm not sure what has happened (or if it is a problem since I don't change my files that often).</p>
<p>git-annex version: 4.20131101</p>
<p>Also running git annex with one ssh remote ( laptop1 & laptop2 synching through a ssh remote server ).</p>
<p>Got a bunch of
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/git-annex does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/master does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/git-annex does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/master does not point to a valid object!
when I tried a manual git annex sync, and noticed that I had a bunch of those in the log in the webapp as well...</p>
<p>The gui doesn't show that anything is wrong, and looking at the log it seems that things are atleast uploading</p>
<pre><code>[2013-11-12 09:05:46 CET] Committer: Committing changes to git
[2013-11-12 09:05:46 CET] Pusher: Syncing with born
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/git-annex does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/master does not point to a valid object!
Everything up-to-date
FILE
32768 42% 0.00kB/s 0:00:00
76972 100% 42.16MB/s 0:00:00 (xfer#1, to-check=0/1)
sent 77056 bytes received 31 bytes 51391.33 bytes/sec
total size is 76972 speedup is 1.00
[2013-11-12 09:05:48 CET] Transferrer: Uploaded FILE
[2013-11-12 09:05:48 CET] Pusher: Syncing with born
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/git-annex does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/master does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/git-annex does not point to a valid object!
error: refs/synced/dbb70cea-4b83-416f-93af-e59082c4d633/master does not point to a valid object!
To ssh://me@born/annex
54e04cf..333cf10 git-annex -> synced/git-annex
</code></pre>
comment 3http://git-annex.branchable.com/forum/Git_annex___39__corrupting__39___itself/comment_3_ab062b1df3b55fd49852a6220c98249e/clacke2013-11-27T22:47:37Z2013-11-12T17:19:32Z
<p>I have been getting this too. Here is what I have done to fix it:</p>
<p><a href="http://git-annex.branchable.com/tips/recovering_from_a_corrupt_git_repository/">recovering from a corrupt git repository</a></p>
comment 3http://git-annex.branchable.com/forum/Git_annex___39__corrupting__39___itself/comment_3_75f957e7be6c1ad8936c0a2a5374db3e/Jonas2013-11-27T22:47:37Z2013-11-13T09:03:24Z
<p>I did a change of one of the files and that totally broke all other repositories, git fsck reports a lot of missing trees (I'm not sure if it is normal), and git annex fsck started reporting invalid object for another file for some reason, also got a (git annex repair still reports everything is fine though.)</p>
<pre><code>fatal: git-write-tree: error building trees
git-annex: failed to read sha from git write-tree
</code></pre>
<p>I tried following those instructions but I don't think I had a good repository, git annex repair reported everything was ok but git fsck said a lot of trees where missing and it stopped updating.
I noticed I was running different git version (git version 1.7.9.5 on the server and git version 1.8.4.2 on one of the clients), so maybe that was part of the reason.</p>
<p>I couldn't find out what remote dbb70cea-4b83-416f-93af-e59082c4d633 was supposed to be either, it wasn't any of the active ones and it didn't show up with git annex status either (I've lost a few repositories when I reinstalled my computer).</p>
<p>I ended up recreating the repository (by copying the raw files) from what I think is the most recent version from one of my computers and hope that it was a error that happened due to upgrades.</p>
comment 4http://git-annex.branchable.com/forum/Git_annex___39__corrupting__39___itself/comment_4_45974f60a81ed2d00b87ffb1a7963c6f/joeyh.name2014-01-13T20:47:18Z2014-01-13T20:27:34Z
Many problems of this sort can happen if the disk that the git reposotory is on is losing data that's written to it, or is just removed (or the computer crashes) at the wrong time. <code>git-annex repair</code> can be run in the repository to recover from many problems like this, and it's getting better all the time.