{"thread":{"id":"36958","subject":"Error 128 Clone succeeded, but checkout failed","startedAt":"2014-06-18T23:03:40Z","lastAt":"2014-06-19T00:37:39Z","messageCount":4,"participants":["warren.l.dodge@tektronix.com","brian m. carlson","Dodge, Warren L"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"244609","messageId":"05c29ee7-8629-424e-b2db-de49db976e55@US-BV-EXH02-P.global.tektronix.net","threadId":"36958","inReplyTo":null,"subject":"Error 128 Clone succeeded, but checkout failed","fromName":"","fromEmail":"warren.l.dodge@tektronix.com","sentAt":"2014-06-18T23:03:40Z","receivedAt":"2014-06-18T23:03:40Z","isPatch":false,"sender":{"key":"warren.l.dodge@tektronix.com","avatar":null},"body":"I have looked for an answer to the Error 128 Clone succeeded, but checkout failed message we are getting on a clone command.\nAnd there does not seem to be any that relates to our situation. \n\nThe repository is on a local file server system that is mounted to the pc as L:\n\nIf we clone the repository on to the L: directory structure we get the following\n\ngit.exe clone      --progress -v  L:\\GIT_REPOSITORY L:\\warrend\\fail\n\nCloning into L:\\warrend\\fail\nDone.\nFatal: unable to read \"Long hash key\"\nWarning: clone succeeded, but checkout failed.\nYou can inspect what was checked out with git status\nAnd retry the checkout with git checkout -f HEAD\n\nGit did not exit cleanly (exit code 128) ( time and date etc)\n\nAt this point there is only a .git directory at the destination\n\nWe have another drive mounted as X: which utilizes a different file server. If we do this\n\ngit.exe clone      --progress -v  L:\\GIT_REPOSITORY X:\\warrend\\works\n\nIt will clone and do the checkout properly.\n\nThese 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.\n\nI copied the two .git directories to a linux file system and did a diff -r of them and found this\n\nBad one doesn't have the putty line for some reason \ndiff -r fail/.git/config  works/.git/config\n12d11\n<       puttykeyfile = \n\nThere was no index file in the bad tree. The config file which is in both trees was made after the index file.\nOnly in .git: index\n\nI was hoping there was a debug method that would allow us to see what the actual check was that is failing.\nAny help on this would be greatly appreciated.\n"},{"id":"244611","messageId":"20140618235539.GL368384@vauxhall.crustytoothpaste.net","threadId":"36958","inReplyTo":"05c29ee7-8629-424e-b2db-de49db976e55@US-BV-EXH02-P.global.tektronix.net","subject":"Re: Error 128 Clone succeeded, but checkout failed","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2014-06-18T23:55:39Z","receivedAt":"2014-06-18T23:55:39Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Wed, Jun 18, 2014 at 04:03:40PM -0700, warren.l.dodge@tektronix.com wrote:\n> git.exe clone      --progress -v  L:\\GIT_REPOSITORY L:\\warrend\\fail\n> \n> Cloning into L:\\warrend\\fail\n> Done.\n> Fatal: unable to read \"Long hash key\"\n> Warning: clone succeeded, but checkout failed.\n> You can inspect what was checked out with git status\n> And retry the checkout with git checkout -f HEAD\n\nWhat git version are you using?\n\nAlso, is this the exact (copy-and-pasted) message you're getting?  There\nare several similar messages starting with \"unable to read\", and knowing\nthe exact error message (including casing) is important in order to be\nable to help you.\n\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"},{"id":"244612","messageId":"20140619002444.GM368384@vauxhall.crustytoothpaste.net","threadId":"36958","inReplyTo":"C8DDA0C887F79C468978FDEF2DA46F9F0145B453@US-BV-EXM01-P.global.tektronix.net","subject":"Re: Error 128 Clone succeeded, but checkout failed","fromName":"brian m. carlson","fromEmail":"sandals@crustytoothpaste.net","sentAt":"2014-06-19T00:24:44Z","receivedAt":"2014-06-19T00:24:44Z","isPatch":false,"sender":{"key":"sandals@crustytoothpaste.net","avatar":"https://avatars.githubusercontent.com/u/497054?v=4"},"body":"On Thu, Jun 19, 2014 at 12:11:43AM +0000, Dodge, Warren L wrote:\n> Hi Brian\n\nHi.  Please do keep the list in CC.  Someone else may be able to help\nyou better than I.\n\n> c:\\Program Files (x86)\\Git\\bin\\git.exe\" --version\n> git version 1.9.4.msysgit.0\n> \n> I also had 1.8.?? and it did the same thing so I updated to try that.\n> \n> This is exact.\n> \"c:\\Program Files (x86)\\Git\\bin\\git.exe\"  clone --progress -v VHDR_GIT_REPOSITORY fail\n> Cloning into 'fail'...\n> done.\n> fatal: unable to read tree a7b8f40dcafba3ec534db6d11e4b928775f26bcd\n\nThis means that git is unable to read this object.  It could be missing\nor corrupt.\n\nWhat do you get if you try to run git fsck --full on this newly cloned\nrepository?  I realize it won't have a working directory, but git fsck\nshould still run.\n\n> warning: Clone succeeded, but checkout failed.\n> You can inspect what was checked out with 'git status'\n> and retry the checkout with 'git checkout -f HEAD'\n> \n> I didn't get the status code but is was 128 when I did this in bash\n> \n> Our file servers are many terabytes and use DFS to break them up into\n> the file systems that are used.\n\nFrom what I can tell of DFS from Wikipedia, it's using SMB under the\nhood, and I'm not sure how well git works over SMB.  Maybe some of the\nmsysgit folks can chime in here?\n\n-- \nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"},{"id":"244613","messageId":"C8DDA0C887F79C468978FDEF2DA46F9F0145B48B@US-BV-EXM01-P.global.tektronix.net","threadId":"36958","inReplyTo":"20140619002444.GM368384@vauxhall.crustytoothpaste.net","subject":"RE: Error 128 Clone succeeded, but checkout failed","fromName":"Dodge, Warren L","fromEmail":"warren.l.dodge@tektronix.com","sentAt":"2014-06-19T00:37:39Z","receivedAt":"2014-06-19T00:37:39Z","isPatch":false,"sender":{"key":"warren.l.dodge@tektronix.com","avatar":null},"body":"Here is the fsck which is ok. Remember that if I do the clone to another file server it works fine.\n\n\"c:\\Program Files (x86)\\Git\\bin\\git.exe\"  fsck --full\nChecking object directories: 100% (256/256), done.\nChecking objects: 100% (774/774), done.\nChecking connectivity: 5128, done.\n\nOne thing I notice now, is that the object key is different on each run of the clone. \n81f1bb353f860726835c6d265b3433a72c3fc082 vs a7b8f40dcafba3ec534db6d11e4b928775f26bcd and others we did yesterday.\n\n\nAlso if we do the suggested command 'git checkout -f HEAD' it works fine.\n\n\n-----Original Message-----\nFrom: brian m. carlson [mailto:sandals@crustytoothpaste.net] \nSent: Wednesday, June 18, 2014 5:25 PM\nTo: Dodge, Warren L\nCc: git@vger.kernel.org\nSubject: Re: Error 128 Clone succeeded, but checkout failed\n\nOn Thu, Jun 19, 2014 at 12:11:43AM +0000, Dodge, Warren L wrote:\n> Hi Brian\n\nHi.  Please do keep the list in CC.  Someone else may be able to help you better than I.\n\n> c:\\Program Files (x86)\\Git\\bin\\git.exe\" --version git version \n> 1.9.4.msysgit.0\n> \n> I also had 1.8.?? and it did the same thing so I updated to try that.\n> \n> This is exact.\n> \"c:\\Program Files (x86)\\Git\\bin\\git.exe\"  clone --progress -v \n> VHDR_GIT_REPOSITORY fail Cloning into 'fail'...\n> done.\n> fatal: unable to read tree a7b8f40dcafba3ec534db6d11e4b928775f26bcd\n\nThis means that git is unable to read this object.  It could be missing or corrupt.\n\nWhat 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.\n\n> warning: Clone succeeded, but checkout failed.\n> You can inspect what was checked out with 'git status'\n> and retry the checkout with 'git checkout -f HEAD'\n> \n> I didn't get the status code but is was 128 when I did this in bash\n> \n> Our file servers are many terabytes and use DFS to break them up into \n> the file systems that are used.\n\n>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?\n\n--\nbrian m. carlson / brian with sandals: Houston, Texas, US\n+1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only\nOpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187\n"}]}