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

Missing Refs after Garbage Collection

From
EGEarl Gresh <egresh@codeaurora.org>
Date
Dec 22, 2012, 01:41 UTC
Message-ID
<C0A16EC8-D05A-41D0-BF2A-34BF3B1B839E@codeaurora.org>
Hi-
I have observed that after running GC, one particular git repository ended up with some missing refs in the refs/changes/* namespace the Gerrit uses for storing patch sets. The refs were valid and should not have been pruned. Concerned about loosing data, GC is still enabled but ref packing is turned off. Now the number of refs has grown to the point that it's causing performance problems when cloning the project.
Is anyone familiar with git gc deleting valid references? I'm running git version 1.7.8. Have there been any patches in later git releases that might address this issue ( if it is a git problem )?
Thanks
Next: Dmitry Potapov
Message 1 of 4 in “Missing Refs after Garbage Collection”
  1. Earl GreshDec 22, 2012
  2. Dmitry PotapovDec 22, 2012
  3. Jeff KingDec 23, 2012
  4. Martin FickJan 2, 2013

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.