Thanks. I know it is hard to get an idea without being able to reproduce it. I think there is no alternative without debugging it with GDB. I’ve tried your suggestions and nothing has changed. I’ve also update the GIT as you suggested, but it is still the same. Just to see, if GIT server causes some issues, I’ve pushed to repo to github public as a private repo, and can reproduce the issue there as well. Thanks for your support. On Tue, Feb 14, 2017 at 10:53 AM, Serdar Sahin <serdar@xxxxxxxxxxxxx> wrote: > Hi Christian, > > Thanks. I know it is hard to get an idea without being able to reproduce it. > I think there is no alternative without debugging it with GDB. > > I’ve tried your suggestions and nothing has changed. > > I’ve also update the GIT as you suggested, but it is still the same. > > Just to see, if GIT server causes some issues, I’ve pushed to repo to github > public as a private repo, and can reproduce the issue there as well. > > Thanks for your support. > > -- > Serdar Sahin > Peak Games > > On Saturday, 11 February 2017 at 15:28, Christian Couder wrote: > > On Wed, Feb 8, 2017 at 11:26 AM, Serdar Sahin <serdar@xxxxxxxxxxxxx> wrote: > > Hi Christian, > > > We are using a private repo (Github Enterprise). > > > Maybe you could try 'git fast-export --anonymize ...' on it. > > Let me give you the > details you requested. > > > On Git Server: git version 2.6.5.1574.g5e6a493 > > On my client: git version 2.10.1 (Apple Git-78) > > > I’ve tried to reproduce it with public repos, but couldn’t do so. > > > You might try using the latest released version (2.11.1). > > For example you could install the last version on the client and then > clone from the server with --bare and use this bare repo as if it was > the server. > > You could also try `git fsck` to see if there are problems on your repo. > > Are there submodules or something a bit special? > > In the end it's difficult for us to help if we cannot reproduce, so > your best bet might be to debug yourself using gdb for example. > > If I > could get an error/log output, that would be sufficient. > > > I am also including the full output below. (also git gc) > > > MacOSX:test serdar$ git clone --mirror --depth 50 --no-single-branch > git@xxxxxxxxxxxxxxxxxxxxx:Casual/code_repository.git > > > You could also try with different options above... > > Cloning into bare repository 'code_repository.git'... > > remote: Counting objects: 3362, done. > > remote: Compressing objects: 100% (1214/1214), done. > > remote: Total 3362 (delta 2335), reused 2968 (delta 2094), pack-reused 0 > > Receiving objects: 100% (3362/3362), 56.77 MiB | 1.83 MiB/s, done. > > Resolving deltas: 100% (2335/2335), done. > > MacOSX:test serdar$ cd code_repository.git/ > > MacOSX:code_repository.git serdar$ GIT_CURL_VERBOSE=1 GIT_TRACE=1 git > fetch --depth 50 origin cc086c96cdffe5c1ac78e6139a7a4b79e7c821ee > > > ... and above. > > Also it looks like you use ssh so something like GIT_SSH_COMMAND="ssh > -vv" might help more than GIT_CURL_VERBOSE=1 > > 13:23:15.648337 git.c:350 trace: built-in: git 'fetch' > '--depth' '50' 'origin' 'cc086c96cdffe5c1ac78e6139a7a4b79e7c821ee' > > 13:23:15.651127 run-command.c:336 trace: run_command: 'ssh' > 'git@xxxxxxxxxxxxxxxxxxxxx' 'git-upload-pack > '\''Casual/code_repository.git'\''' > > 13:23:17.750015 run-command.c:336 trace: run_command: 'gc' '--auto' > > 13:23:17.750829 exec_cmd.c:189 trace: exec: 'git' 'gc' '--auto' > > 13:23:17.753983 git.c:350 trace: built-in: git 'gc' '--auto' > > MacOSX:code_repository.git serdar$ echo $? > > 1 > > MacOSX:code_repository.git serdar$ GIT_CURL_VERBOSE=1 GIT_TRACE=1 git gc > --auto > > 13:23:45.899038 git.c:350 trace: built-in: git 'gc' '--auto' > > MacOSX:code_repository.git serdar$ echo $? > > 0 > >