git - Git "Could not read"错误如何处理

Question

我在我的 git 存储库中收到此错误:

22:09:15 $ git status
# On branch master
error: Could not read 8124cc15c63be92d534e4cdfa33c38d54deee122
error: unable to read tree object HEAD
nothing to commit (working directory clean)

Google 搜索 error: unable to read tree object HEAD 没有太大帮助，这个错误似乎非常罕见。我不确定如何处理它。会不会是硬盘故障？

编辑:git fsck 的输出如下:

broken link from  commit 607328dc80e4901a55b95c683d4fbf43e6df28bf
              to    tree 8124cc15c63be92d534e4cdfa33c38d54deee122
missing tree 8124cc15c63be92d534e4cdfa33c38d54deee122
dangling tree 56b5d4a5e429d251582ec927bca7ef1225510c41
dangling tree 0259d2d38b18b6136bb6070fb41faf3624453cc6

Answer 1

在“断开的链接”消息中，您可以关注 GitFaq recommendations :

• back up all your state so that anything you do is re-doable if you corrupt things more!
• explode any corrupt pack-files
  • See "man git-unpack-objects", and in particular the "-r" flag.
    Also, please realize that it only unpacks objects that aren't already available, so you need to move the pack-file away from its normal location first (otherwise git-unpack-objects will find all objects that are in the pack-file in the pack-file itself, and not unpack anything at all)
• replace any broken and/or missing objects
  • This is the challenging part.
    Sometimes (hopefully often!) you can find the missing objects in other copies of the repositories.
    At other times, you may need to try to find the data some other way (for example, maybe your checked-out copy contains the file content that when hashed will be the missing object?).
• make sure everything is happy with "git fsck --full"
• repack everything to get back to an efficient state again

---

注意事项:

• 丢失的对象也可以是related to alternate (当你 share objects between repositories )与 git alternates (即使是 can be risky )。
• JGit/Egit eclipse 插件也为 have a few issues 所熟知。 .
  (2012 年 2 月更新:those plugins 已经取得了长足的进步，现在非常稳定)

2016 年 7 月更新(7 年后)，Git 2.10 即将发布，您现在拥有:

git fsck --name-objects

它有助于命名那些失效链接的来源

有关更多信息，请参阅“How to fix git error broken link from tree to tree?”。