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

corrupt repos does not return error with `git fsck`

From
FMFaheem Mitha <faheem@faheem.info>
Date
May 20, 2015, 16:17 UTC
Message-ID
<alpine.DEB.2.11.1505202142540.9343@orwell.homelinux.org>
Hi,
Clone the repos https://github.com/fmitha/SICL.
Then
     git show 280c12ab49223c64c6f914944287a7d049cf4dd0
gives
     fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0
But
     git fsck
gives
     Checking object directories: 100% (256/256), done.
     Checking objects: 100% (49356/49356), done.

So `git fsck` does not return an error, though the repos is corrupt. This may be of interest to the developers.

Please CC me on any reply, I'm not subscribed to the list. Thanks.
                                             Regards, Faheem Mitha
Next: Matthieu Moy
Message 1 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.