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

Re: [PUB]corrupt repos does not return error with `git fsck`

From
FMFaheem Mitha <faheem@faheem.info>
Date
May 20, 2015, 17:58 UTC
Message-ID
<alpine.DEB.2.11.1505202256330.9343@orwell.homelinux.org>
In-Reply-To
<vpq382rkvzf.fsf@anie.imag.fr>
On Wed, 20 May 2015, Matthieu Moy wrote:
> Faheem Mitha <faheem@faheem.info> writes:
>> Hi,
>> Clone the repos https://github.com/fmitha/SICL.
>> Then
>>     git show 280c12ab49223c64c6f914944287a7d049cf4dd0
>> gives
>>     fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0
> It seems 280c12ab49223c64c6f914944287a7d049cf4dd0 is not an object in
> your repository. The good news it: I don't think you have a corrupt
> repository. What makes you think you have an object with identifier
> 280c12ab49223c64c6f914944287a7d049cf4dd0?

I was going by the answer (by CodeWizard) in http://stackoverflow.com/q/30348615/350713

The question there also gives the context of this question.

The repos I referenced in my post to the git mailing list just now, is just a clone of https://github.com/drmeister/SICL.

If I just give a random hash to `git show` in that repos, I get
     fatal: ambiguous argument '...': unknown revision or path not in the working tree.

It seemed reasonable to assume (based on what little knowledge I had about) that the 280c12ab49223c64c6f914944287a7d049cf4dd0 commit was the problem.

However, this repos is a fork of another repos, namely https://github.com/robert-strandh/SICL

That repos contains more recent commits than the fork does.

If I take any of the more recent commits from that repos, and try the hash with `git show`, i.e.

     git show <hash>

in the fork, I get the same error, which makes to me think something else must be going on.

Chris (drmeister) has modified the path the submodule is obtained from, so the instructions in the SO question won't work as a reproduction recipe any more, but if you want to take a look I could clone his repos and set it up the same way it was. Let me know.

                                                     Regards, Faheem Mitha
Previous: Matthieu MoyNext: Matthieu Moy
Message 18 of 19 in “corrupt repos does not return error with `git fsck`”
  1. Faheem MithaMay 20, 2015
  2. Matthieu MoyMay 20, 2015
  3. Johannes SchindelinMay 20, 2015
  4. Stefan BellerMay 20, 2015
  5. John KeepingMay 20, 2015
  6. Jeff KingMay 20, 2015
  7. Jeff KingMay 20, 2015
  8. Junio C HamanoMay 20, 2015
  9. Stefan BellerMay 20, 2015
  10. Junio C HamanoMay 20, 2015
  11. Stefan BellerMay 20, 2015
  12. Jeff KingMay 20, 2015
  13. Junio C HamanoMay 20, 2015
  14. Faheem MithaMay 20, 2015
  15. Stefan BellerMay 20, 2015
  16. Faheem MithaMay 20, 2015
  17. Matthieu MoyMay 20, 2015
  18. Faheem MithaMay 20, 2015
  19. Matthieu MoyMay 21, 2015

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.