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

From: Patrick Steinhardt <[email-masked]>
Date: Fri, 10 Apr 2026 14:31:10 +0200

On Fri, Apr 10, 2026 at 09:20:20AM +0200, Pascal Chambon wrote:
> 
> 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