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

Re: Bug - git fsck never ending on git-for-windows

From
Patrick Steinhardt <ps@pks.im>
Date
Apr 10, 2026, 12:31 UTC
Message-ID
<adjtjv76Th_lPRKv@pks.im>
In-Reply-To
<a07a6a49-0520-44c7-b9c5-2173465cc1ca@gmail.com>
On Fri, Apr 10, 2026 at 09:20:20AM +0200, Pascal Chambon wrote:
Show 29 quoted lines
> 
> What did you do before the bug happened? (Steps to reproduce your issue)
> 
> > I launched "git fsck" (with various arguments)
> 
> What did you expect to happen? (Expected behavior)
> 
> > A long run of fsck and then it's over
> 
> What happened instead? (Actual behavior)
> 
> > A (seemingly) neverending run of fsck, exceeding the expected count of
> objects to check:
> > $ git fsck
> > Checking ref database: 100% (1/1), done.
> > Checking object directories: 100% (256/256), done.
> > Checking objects: 190% (54090/28351)        -->  (process still
> turning...)
> 
> What's different between what you expected and what actually happened?
> 
> > Normal, finished fsck run, vs neverending checking of objects.
> 
> Anything else you want to add:
> 
> > This is a quite old repository (from 2012) with quite heavy media files in
> it (70 GB total).
> > I've tried to "git gc --aggressive", it worked, and pack files are
> numerous and about the same size, but the fsck anomally remains.

This strongly reminds me of the issue fixed in 13eb65d366 (pack-check: fix verification of large objects, 2026-02-23), which is going to be released with Git 2.54. Could you maybe verify whether that commit fixes the issue you're observing?

Thanks!
Patrick
Previous: Pascal Chambon
Message 2 of 2 in “Bug - git fsck never ending on git-for-windows”
  1. Pascal ChambonApr 10, 2026
  2. Patrick SteinhardtApr 10, 2026

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.