Git reset = fatal: unable to read tree

Question

Someone made a commit on the wrong branch so I tried to move the commit to another branch. When I tried to roll back the commit, I got this error:

[user@server gitrepo]$ git reset --hard 9c2de3c0 fatal: unable to read tree 9c2de3c0af09fc07a84ff84b594beb5a6d489181

The object looks fine:

[user@server gitrepo]$ ls objects/9c/2de3c* -al -r--r--r-- 1 git git 222 Aug 28 12:09 objects/9c/2de3c0af09fc07a84ff84b594beb5a6d489181

Why can't it read this object, and what do I do about that?

Edit: to distinguish my problem from others:

Git's database doesn't appear to be particularly out of sorts. Running git fsck -full shows only a few (~20) dangling blobs and one dangling commit. Which does not seem particularly alarming.

@Gabriele: I looked at that post, but that question, and it's answer, pertain to a broken link from commit. I have no such error when I run git fsck. — doub1ejack
– doub1ejack, Commented Aug 29, 2013 at 16:54
1) what does git cat-file -t 9c2de3c0 show? 2) what does git cat-file -p 9c2de3c0 show? (I suspect at least one will also fail, but it's worth a quick poke at it) — torek
– torek, Commented Aug 29, 2013 at 18:54
@torek - 1) git cat-file -t 9c2de3c0 = 'commit' 2) git cat-file -p 9c2de3c0 = my message, 'MODULE: added similarterms (MM)' — doub1ejack
– doub1ejack, Commented Aug 29, 2013 at 20:10
Hm, what about the "tree" and "parents" parts (in the -p output)? If you follow those IDs do they work? — torek
– torek, Commented Aug 29, 2013 at 20:16

Mark Bowler · Accepted Answer · 2013-11-26 05:12:29Z

2

I've got the same problem. Solved it by checking and fixing disk. Some files were corrupted.

answered Nov 26, 2013 at 5:12

1041 silver badge3 bronze badges

Sign up to request clarification or add additional context in comments.

1 Answer 1