From: Patrick Steinhardt <ps@pks.im>
To: Pascal Chambon <pythoniks@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Bug - git fsck never ending on git-for-windows
Date: Fri, 10 Apr 2026 14:31:10 +0200 [thread overview]
Message-ID: <adjtjv76Th_lPRKv@pks.im> (raw)
In-Reply-To: <a07a6a49-0520-44c7-b9c5-2173465cc1ca@gmail.com>
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
prev parent reply other threads:[~2026-04-10 12:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-10 7:20 Bug - git fsck never ending on git-for-windows Pascal Chambon
2026-04-10 12:31 ` Patrick Steinhardt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adjtjv76Th_lPRKv@pks.im \
--to=ps@pks.im \
--cc=git@vger.kernel.org \
--cc=pythoniks@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox