On Thu, Jun 19, 2014 at 12:11:43AM +0000, 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 
> 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

Attachment: signature.asc
Description: Digital signature

Reply via email to