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

Re: What's going on here? Bad repo, no error locally?

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 22, 2009, 05:06 UTC
Message-ID
<7vws9d46q9.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<450196A1AAAE4B42A00A8B27A59278E70ACE053E@EXCHANGE.trad.tradestation.com>
"John Dlugosz" <JDlugosz@TradeStation.com> writes:
Show 7 quoted lines
> Developer B runs git fsck --full, gets no errors but one dangling blob.
> Does a push.  No errors.
> Now, on the upstream repo, I run fsck, and find a bunch of danglings (as
> always) and a missing blob.
> Any fetch from that repo will fail, due to that missing blob.
>
> What's going on?  How can I fix his local repository, other than...

It sounds like there is nothing to fix in "his local repository"; the error is in your "upstream repo".

The dangling objects can happen if you push over dumb transport and interrupt in the middle, or you force a push of a rewound branch, so it does not necessarily indicate any errors, but a missing object is always an error.

Previous: Bryan DonlanNext: John Dlugosz
Message 5 of 7 in “What's going on here? Bad repo, no error locally?”
  1. John DlugoszApr 22, 2009
  2. Bryan DonlanApr 22, 2009
  3. John M. DlugoszApr 22, 2009
  4. Bryan DonlanApr 22, 2009
  5. Junio C HamanoApr 22, 2009
  6. John DlugoszApr 22, 2009
  7. Brandon CaseyApr 22, 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.