Re: Error 128 Clone succeeded, but checkout failed
On Wed, Jun 18, 2014 at 04:03:40PM -0700, warren.l.do...@tektronix.com wrote: 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 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. -- 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 signature.asc Description: Digital signature
Re: Error 128 Clone succeeded, but checkout failed
On Thu, Jun 19, 2014 at 12:11:43AM +, Dodge, Warren L wrote: Hi Brian Hi. Please do keep the list in CC. Someone else may be able to help you better than I. c:\Program Files (x86)\Git\bin\git.exe --version git version 1.9.4.msysgit.0 I also had 1.8.?? and it did the same thing so I updated to try that. This is exact. c:\Program Files (x86)\Git\bin\git.exe clone --progress -v VHDR_GIT_REPOSITORY fail Cloning into 'fail'... done. fatal: unable to read tree a7b8f40dcafba3ec534db6d11e4b928775f26bcd 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. 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' I didn't get the status code but is was 128 when I did this in bash Our file servers are many terabytes and use DFS to break them up into the file systems that are used. 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? -- 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 signature.asc Description: Digital signature
RE: Error 128 Clone succeeded, but checkout failed
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:sand...@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 +, Dodge, Warren L wrote: Hi Brian Hi. Please do keep the list in CC. Someone else may be able to help you better than I. c:\Program Files (x86)\Git\bin\git.exe --version git version 1.9.4.msysgit.0 I also had 1.8.?? and it did the same thing so I updated to try that. This is exact. c:\Program Files (x86)\Git\bin\git.exe clone --progress -v VHDR_GIT_REPOSITORY fail Cloning into 'fail'... done. fatal: unable to read tree a7b8f40dcafba3ec534db6d11e4b928775f26bcd 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. 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' I didn't get the status code but is was 128 when I did this in bash Our file servers are many terabytes and use DFS to break them up into the file systems that are used. 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? -- 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 -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
