git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Recovering from gc errors

From
Jeff King <peff@peff.net>
Date
Nov 15, 2017, 00:19 UTC
Message-ID
<20171115001907.vno7fo4t4bglh35n@sigill.intra.peff.net>
In-Reply-To
<3af0f8cc-09f3-bcf2-04c8-f076e0ddcea2@xiplink.com>
On Tue, Nov 14, 2017 at 10:39:31AM -0500, Marc Branchaud wrote:
Show 7 quoted lines
> >    rm -rf .git/logs
> 
> Unfortunately, removing the logs directory does not fix "git gc".  So I
> restored it.
> 
> However I did find all of the bad SHAs in the HEAD logs of four of my
> worktrees.

Ah, right. There are more logs than .git/logs these days. That makes sense.

> I'm willing to chalk this up to bugs in the early worktree code, unless one
> of the CC'd worktree developers thinks otherwise.

Perhaps fixed by acd9544a8f (revision.c: --reflog add HEAD reflog from all worktrees, 2017-08-23). I think before then that prune/repack would consider those objects unreachable.

-Peff
Previous: Eric Sunshine
Message 5 of 5 in “Recovering from gc errors”
  1. Marc BranchaudNov 13, 2017
  2. Jeff KingNov 14, 2017
  3. Marc BranchaudNov 14, 2017
  4. Eric SunshineNov 14, 2017
  5. Jeff KingNov 15, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.