3

The repository's size is over 1GB, when i pull up to 50%, error occurred:

> remote: Counting objects: 23891, done. remote: Compressing objects:
> 100% (19980/19980), done. fatal: The remote end hung up
> unexpectedly3.61 MiB | 333 KiB/s    fatal: early EOF fatal: recursion
> detected in die handler

Can anybody help me, please?

Khoi Ngo
  • 941
  • 8
  • 16
  • If you have a 1GB repo, you arguably have bigger problems. – Oliver Charlesworth Oct 09 '14 at 19:12
  • 3
    Not necessarily. We keep some static content in our repo structure and they reach GB+ at times. – isherwood Oct 09 '14 at 19:17
  • 1
    possible duplicate of [GitHub Clone Error: Cannot clone with EOF error](http://stackoverflow.com/questions/18557703/github-clone-error-cannot-clone-with-eof-error) – isherwood Oct 09 '14 at 19:18
  • @isherwood The OP doesn't seem to mention using GitHub. Also, this question is somewhat within the scope of Stack Overflow, but needs more details and troubleshooting. – JasonMArcher Oct 09 '14 at 20:43
  • There are other proposed solutions there than the one referring to Github. Also, "possible". – isherwood Oct 09 '14 at 20:43

2 Answers2

4

I also agree with isherwood that it's most likely a copy of StackOverflow: GitHub Clone Error: Cannot clone with EOF error, however that entry was very disappointing for me (at the time there was just one response, which did not help me).

I resolved it with the following steps (found on the internet, not on StackOverflow)

  1. git clone --depth 1 YOUR-URL-TO-CLONE ./
  2. git fetch --unshallow
  3. git pull

For more information about the meaning of 1., i.e., a shallow clone, see StackOverflow: Is it safe to shallow clone with --depth 1, create commits, and pull updates again?

For more information about the meaning of 2., see StackOverflow: https://stackoverflow.com/questions/6802145/how-to-convert-a-git-shallow-clone-to-a-full-clone.

Regarding 3: This is, I believe, just to double-check. At least for me that did not bring me any updates.

Prof.Chaos
  • 895
  • 8
  • 22
1

It will most likely fail due to the size of your repository.

If you have access to the remote repository, try this:

  1. Get a copy of the remote repository files. You can tar.gz the remote repository directory and download it to your local machine.
  2. Unzip the remote repository somewhere in your local machine.

  3. Clone the repository from your machine (no file downloading here so it should work)

    git clone /path/to/where/you/unzipped/the/remote/repository your_local_copy

  4. Edit the .git/config file you can find inside 'your_local_copy' directory

  5. Edit the value of the 'url' key just below the [remote "origin"] line.

    [remote "origin"]

    url = git+ssh://youruser@yourrepositoryhost/srv/git/yourrepository.git

  6. Your local repository will now point to the remote repository and should work as expected.

  7. Remove the copy of the remote repository you made in Step 2.
gmarintes
  • 1,288
  • 12
  • 16