{"thread":{"id":"65466","subject":"Bug - git fsck never ending on git-for-windows","startedAt":"2026-04-10T07:20:23Z","lastAt":"2026-04-10T12:31:16Z","messageCount":2,"participants":["Pascal Chambon","Patrick Steinhardt"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"541329","messageId":"a07a6a49-0520-44c7-b9c5-2173465cc1ca@gmail.com","threadId":"65466","inReplyTo":null,"subject":"Bug - git fsck never ending on git-for-windows","fromName":"Pascal Chambon","fromEmail":"pythoniks@gmail.com","sentAt":"2026-04-10T07:20:20Z","receivedAt":"2026-04-10T07:20:23Z","isPatch":false,"body":"\nWhat did you do before the bug happened? (Steps to reproduce your issue)\n\n > I launched \"git fsck\" (with various arguments)\n\nWhat did you expect to happen? (Expected behavior)\n\n > A long run of fsck and then it's over\n\nWhat happened instead? (Actual behavior)\n\n > A (seemingly) neverending run of fsck, exceeding the expected count \nof objects to check:\n > $ git fsck\n > Checking ref database: 100% (1/1), done.\n > Checking object directories: 100% (256/256), done.\n > Checking objects: 190% (54090/28351)        -->  (process still \nturning...)\n\nWhat's different between what you expected and what actually happened?\n\n > Normal, finished fsck run, vs neverending checking of objects.\n\nAnything else you want to add:\n\n > This is a quite old repository (from 2012) with quite heavy media \nfiles in it (70 GB total).\n > I've tried to \"git gc --aggressive\", it worked, and pack files are \nnumerous and about the same size, but the fsck anomally remains.\n\n\n[System Info]\ngit version:\ngit version 2.53.0.windows.2\ncpu: x86_64\nbuilt from commit: e9edee0b34751bf4d7d1feda0e2535bff64d4e77\nsizeof-long: 4\nsizeof-size_t: 8\nrust: disabled\nfeature: fsmonitor--daemon\ngettext: enabled\nlibcurl: 8.18.0\nOpenSSL: OpenSSL 3.5.5 27 Jan 2026\nzlib: 1.3.1\nSHA-1: SHA1_DC\nSHA-256: SHA256_BLK\ndefault-ref-format: files\ndefault-hash: sha1\nuname: Windows 10.0 26200 -> actually Windows 11 Professionnel 25H2\ncompiler info: gnuc: 15.2\nlibc info: no libc information available\n$SHELL (typically, interactive shell): <unset>\n\n\n[Enabled Hooks]\n(none)\n\n"},{"id":"541364","messageId":"adjtjv76Th_lPRKv@pks.im","threadId":"65466","inReplyTo":"a07a6a49-0520-44c7-b9c5-2173465cc1ca@gmail.com","subject":"Re: Bug - git fsck never ending on git-for-windows","fromName":"Patrick Steinhardt","fromEmail":"ps@pks.im","sentAt":"2026-04-10T12:31:10Z","receivedAt":"2026-04-10T12:31:16Z","isPatch":false,"body":"On Fri, Apr 10, 2026 at 09:20:20AM +0200, Pascal Chambon wrote:\n> \n> What did you do before the bug happened? (Steps to reproduce your issue)\n> \n> > I launched \"git fsck\" (with various arguments)\n> \n> What did you expect to happen? (Expected behavior)\n> \n> > A long run of fsck and then it's over\n> \n> What happened instead? (Actual behavior)\n> \n> > A (seemingly) neverending run of fsck, exceeding the expected count of\n> objects to check:\n> > $ git fsck\n> > Checking ref database: 100% (1/1), done.\n> > Checking object directories: 100% (256/256), done.\n> > Checking objects: 190% (54090/28351)        -->  (process still\n> turning...)\n> \n> What's different between what you expected and what actually happened?\n> \n> > Normal, finished fsck run, vs neverending checking of objects.\n> \n> Anything else you want to add:\n> \n> > This is a quite old repository (from 2012) with quite heavy media files in\n> it (70 GB total).\n> > I've tried to \"git gc --aggressive\", it worked, and pack files are\n> numerous and about the same size, but the fsck anomally remains.\n\nThis strongly reminds me of the issue fixed in 13eb65d366 (pack-check:\nfix verification of large objects, 2026-02-23), which is going to be\nreleased with Git 2.54. Could you maybe verify whether that commit fixes\nthe issue you're observing?\n\nThanks!\n\nPatrick\n"}]}