cmhughes cmhughes - 4 months ago 96
Git Question

How to diagnose and fix git fatal: unable to read tree

I'm using

git
to manage files on a project, and keep running into this problem.

When I run
git status
I get the message

fatal: unable to read tree e2d920161d41631066945a3cbcd1b043de919570


As I understand it, I should check the output of
git fsck
, and I receive

broken link from tree e09a42f248afff64336fbbec2523df97c26451ac
to tree e2d920161d41631066945a3cbcd1b043de919570
broken link from tree e09a42f248afff64336fbbec2523df97c26451ac
to tree 9b0dd389bd7f9e8d257395d57e0881b7957f9698
broken link from tree e09a42f248afff64336fbbec2523df97c26451ac
to tree 9e288a4ad60d63f342dfd18237980674426aa725
broken link from tree e09a42f248afff64336fbbec2523df97c26451ac
to tree 2a04647337089f554fab8c49cfd37149e5f4fc9f
broken link from tree e09a42f248afff64336fbbec2523df97c26451ac
to tree ea16658b45ce961adc3c3f519b0e8d9672918ca8


together with a lot of
missing blob
messages.

Following various resources (e.g Git - Broken Links, Missing & Dangling Trees) I have simply re-cloned the project from
github
and started again.

Once I have re-cloned the project, all is good for a few
commit
s, and then the problem arises again. Re-cloning every time doesn't seem to be optimal, and seems to go against the idea of using
git
, and I'd like to try and understand what is going on. How can I diagnose and fix this problem?

Answer

Following my older recommendation, it boils down to being able to find a repo which actually contains the missing elements (here full trees).
This is what is shown in "How to fix corrupted git repository?".

But if a full clone doesn't solve the problem, then it may be:


Update July 2016, with Git 2.10 soon to be release, you now have:

git fsck --name-objects

See "How to fix git error broken link from tree to tree?" for more.