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

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

From
PCPascal Chambon <pythoniks@gmail.com>
Date
Apr 10, 2026, 07:20 UTC
Message-ID
<a07a6a49-0520-44c7-b9c5-2173465cc1ca@gmail.com>
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.
[System Info]
git version:
git version 2.53.0.windows.2
cpu: x86_64
built from commit: e9edee0b34751bf4d7d1feda0e2535bff64d4e77
sizeof-long: 4
sizeof-size_t: 8
rust: disabled
feature: fsmonitor--daemon
gettext: enabled
libcurl: 8.18.0
OpenSSL: OpenSSL 3.5.5 27 Jan 2026
zlib: 1.3.1
SHA-1: SHA1_DC
SHA-256: SHA256_BLK
default-ref-format: files
default-hash: sha1
uname: Windows 10.0 26200 -> actually Windows 11 Professionnel 25H2
compiler info: gnuc: 15.2
libc info: no libc information available
$SHELL (typically, interactive shell): <unset>

[Enabled Hooks] (none)

Next: Patrick Steinhardt
Message 1 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.