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

Re: rogue tree objects, how to diagnose?

From
Jeff King <peff@peff.net>
Date
Mar 1, 2009, 03:46 UTC
Message-ID
<20090301034632.GA318@coredump.intra.peff.net>
In-Reply-To
<20090228.194454.05711858.davem@davemloft.net>
On Sat, Feb 28, 2009 at 07:44:54PM -0800, David Miller wrote:
Show 11 quoted lines
> > "bad object" is about an object that did not parse correctly, as opposed
> > to one that is missing. So it's possible that your repository is
> > corrupted.
> 
> I see.
> 
> I GC and repack my local repos a lot, maybe it happened during
> one of those.
> 
> Thanks a lot Jeff, I'll try to fix the corruption using the
> suggestions you gave me.

If it is real corruption, you might want to save a copy of the repository. I think Linus and Nicolas like to pick apart corruption to figure out if it is a git bug or a disk failure.

-Peff
Previous: David MillerNext: David Miller
Message 4 of 8 in “rogue tree objects, how to diagnose?”
  1. David MillerMar 1, 2009
  2. Jeff KingMar 1, 2009
  3. David MillerMar 1, 2009
  4. Jeff KingMar 1, 2009
  5. David MillerMar 1, 2009
  6. David MillerMar 1, 2009
  7. Junio C HamanoMar 1, 2009
  8. David MillerMar 1, 2009

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.