Error 128 Clone succeeded, but checkout failed

I have looked for an answer to the Error 128 Clone succeeded, but checkout failed message we are getting on a clone command. And there does not seem to be any that relates to our situation.

The repository is on a local file server system that is mounted to the pc as L:

If we clone the repository on to the L: directory structure we get the following

git.exe clone      --progress -v  L:\GIT_REPOSITORY L:\warrend\fail

Cloning into L:\warrend\fail
Done.
Fatal: unable to read "Long hash key"
Warning: clone succeeded, but checkout failed.
You can inspect what was checked out with git status
And retry the checkout with git checkout -f HEAD

Git did not exit cleanly (exit code 128) ( time and date etc)

At this point there is only a .git directory at the destination

We have another drive mounted as X: which utilizes a different file server. If we do this

git.exe clone      --progress -v  L:\GIT_REPOSITORY X:\warrend\works

It will clone and do the checkout properly.

These does not seem to be any permission or disk space problems on the L: drive. We are unable to figure out why this is happening.

I copied the two .git directories to a linux file system and did a diff -r of them and found this

Bad one doesn't have the putty line for some reason diff -r fail/.git/config works/.git/config 12d11 < puttykeyfile =

There was no index file in the bad tree. The config file which is in both trees was made after the index file. Only in .git: index

I was hoping there was a debug method that would allow us to see what the actual check was that is failing. Any help on this would be greatly appreciated.

On Wed, Jun 18, 2014 at 04:03:40PM -0700, warren.l.dodge@tektronix.com wrote:

What git version are you using?

Also, is this the exact (copy-and-pasted) message you're getting? There are several similar messages starting with "unable to read", and knowing the exact error message (including casing) is important in order to be able to help you.

On Thu, Jun 19, 2014 at 12:11:43AM +0000, Dodge, Warren L wrote:

Hi. Please do keep the list in CC. Someone else may be able to help you better than I.

This means that git is unable to read this object. It could be missing or corrupt.

What do you get if you try to run git fsck --full on this newly cloned repository? I realize it won't have a working directory, but git fsck should still run.

From what I can tell of DFS from Wikipedia, it's using SMB under the hood, and I'm not sure how well git works over SMB. Maybe some of the msysgit folks can chime in here?

Here is the fsck which is ok. Remember that if I do the clone to another file server it works fine.

"c:\Program Files (x86)\Git\bin\git.exe" fsck --full Checking object directories: 100% (256/256), done. Checking objects: 100% (774/774), done. Checking connectivity: 5128, done.

One thing I notice now, is that the object key is different on each run of the clone. 81f1bb353f860726835c6d265b3433a72c3fc082 vs a7b8f40dcafba3ec534db6d11e4b928775f26bcd and others we did yesterday.

Also if we do the suggested command 'git checkout -f HEAD' it works fine.

-----Original Message-----
From: brian m. carlson [mailto:sandals@crustytoothpaste.net] 
Sent: Wednesday, June 18, 2014 5:25 PM
To: Dodge, Warren L
Cc: git@vger.kernel.org
Subject: Re: Error 128 Clone succeeded, but checkout failed

On Thu, Jun 19, 2014 at 12:11:43AM +0000, Dodge, Warren L wrote:

Hi.  Please do keep the list in CC.  Someone else may be able to help you better than I.

This means that git is unable to read this object.  It could be missing or corrupt.

What do you get if you try to run git fsck --full on this newly cloned repository?  I realize it won't have a working directory, but git fsck should still run.

--
brian m. carlson / brian with sandals: Houston, Texas, US
+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only
OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187