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

Re: git fsck not identifying corrupted packs

From
Matthieu Moy <matthieu.moy@grenoble-inp.fr>
Date
Oct 20, 2009, 06:24 UTC
Message-ID
<vpq3a5etwfm.fsf@bauges.imag.fr>
In-Reply-To
<200910191307.56989.wjl@icecavern.net>
"Wesley J. Landaker" <wjl@icecavern.net> writes:
> Until I read this thread, I didn't realize you needed --full to check
> objects in packs.
Same here.
> -	OPT_BOOLEAN(0, "full", &check_full, "also consider alternate objects"),
> +	OPT_BOOLEAN(0, "full", &check_full, "also consider packs and alternate objects"),

IMHO, something like this should be applied to "maint", this is kind of a serious bug indeed. Just check the "alternate" thing, according to Junio:

Junio C Hamano <gitster@pobox.com> writes:
Show 5 quoted lines
>     Side note.  I think the help description of --full option is wrong (or
>     at least stale).  We always look at alternate object store these days
>     since e15ef66 (fsck: check loose objects from alternate object stores
>     by default, 2009-01-30).  It probably should read "check packed
>     objects fully" or something.
-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/
Previous: Wesley J. LandakerNext: Gabor Gombas
Message 20 of 21 in “git fsck not identifying corrupted packs”
  1. Sergio CallegariOct 19, 2009
  2. Johannes SixtOct 19, 2009
  3. Johannes SchindelinOct 19, 2009
  4. Junio C HamanoOct 19, 2009
  5. Wesley J. LandakerOct 19, 2009
  6. Robin RosenbergOct 20, 2009
  7. Wesley J. LandakerOct 20, 2009
  8. Matthieu MoyOct 20, 2009
  9. Junio C HamanoOct 20, 2009
  10. Alex RiesenOct 20, 2009
  11. Johannes SchindelinOct 20, 2009
  12. Matthieu MoyOct 20, 2009
  13. fsck: default to "git fsck --full"Junio C Hamano, Oct 20, 2009
  14. Nicolas PitreOct 20, 2009
  15. Junio C HamanoOct 20, 2009
  16. Nicolas PitreOct 20, 2009
  17. Alex RiesenOct 20, 2009
  18. Sergio CallegariOct 19, 2009
  19. Wesley J. LandakerOct 19, 2009
  20. Matthieu MoyOct 20, 2009
  21. Gabor GombasOct 19, 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.