4

My system is Windows 11. I am using latest git bash from 2025-06-28.

I am trying to clone the public github repository https://github.com/eringee/biodata (over HTTPS) / [email protected]:eringee/biodata (over SSH). The complete repository is a bit under 6 megabytes in size.

  • It always works with https
  • If I clone it in /c/dev it works with SSH 60% of the time
  • If I clone it in /d/dev it works with SSH maybe 5% of the time

The failure is: it consistently gets stuck at

Cloning into 'biodata'... remote: Enumerating objects: 991, done. remote: Counting objects: 100% (293/293), done. remote: Compressing objects: 100% (172/172), done. Receiving objects: 36% (357/991)

Then, after some timeout:

fetch-pack: unexpected disconnect while reading sideband packet fatal: early EOF fatal: fetch-pack: invalid index-pack output

If i don't wait until the timeout the only way I have to stop the process is through taskkill /IM git.exe /F but maybe that's just windows being windows.

I tried various settings, from an empty .gitconfig to this:

[core] askpass = compression = 0 eol = lf autocrlf = false fileMode = false ignoreStat = false packedGitLimit = 512m packedGitWindowSize = 512m [user] email = [email protected] name = Jean-Michaël Celerier [filter "lfs"] smudge = git-lfs smudge -- %f process = git-lfs filter-process required = true clean = git-lfs clean -- %f [http] postBuffer = 1548576000 maxRequestBuffer = 200M [ssh] postBuffer = 1548576000 maxRequestBuffer = 200M [pack] window = 1 deltaCacheSize = 2047m packSizeLimit = 2047m windowMemory = 2047m

I am a bit at loss at what else I can try.

Improve this question
8
  • 1
    Maybe some Antivirus/Firewall software is interacting with git. Commented Jun 28 at 16:25
  • I don't have any installed on my computer outside of the windows one (and the folders in question are excluded) Commented Jun 28 at 17:28
  • 3
    This question is similar to: fatal: early EOF fatal: index-pack failed. If you believe it’s different, please edit the question, make it clear how it’s different and/or how the answers on that question are not helpful for your problem. - Sorry, you just didn't mention what you had tried to avoid the issue - from what I can see, you tried this: stackoverflow.com/a/29355320/15167500 Commented Jun 29 at 17:57
  • This certainly feels like a dup to the mentioned question. Though, I am curious, what's the difference between C and D on your machine? Either that's not relevant and is just a coincidence due to having too small of a sample set, or it is relevant and may help point to the underlying cause of the error to begin with. Commented Jun 30 at 16:33
  • 1
    Most of the time when I have file system related Git errors, it's because I have at least one application open (perhaps an IDE such as VS Code with Git extensions running) which is continuously scanning a Git repo, and I do stuff out from under it with the command line, such as rebase or switching branches which heavily modifies the file system. If you are repeatedly deleting and re-cloning a folder for testing purposes, and if something is open and trying to continuously read that folder, maybe it's locking it up somehow... Commented Jul 1 at 15:22
Load 7 more related questions Show fewer related questions

0

Reset to default

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.