Git issue clone issue with .gdb , .loz, & .las files

Git issue clone issue with .gdb , .loz, & .las files

[Robert Brown]

Hi team,

I started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. 

So far we have noticed  .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.  

We are currently testing locally, the repo and the clone exist on the same physical PC
Windows 20H2 (OS Build 19042.1645)
git version 2.36.1.windows.1 (64bit)
git-lfs/3.1.4 (GitHub; windows amd64; go 1.17.8)

Original GitHub Thread
https://github.com/git-lfs/git-lfs/discussions/5005

Robert Brown | Sr. Performance Engineer
Esri | 380 New York Street | Redlands, CA 92373 | USA
T (909) 793-2853 x6618 | mailto:rbrown@esri.com | http://www.esri.com/ 

THE SCIENCE OF WHERE ®

Re: Git issue clone issue with .gdb , .loz, & .las files

[brian m. carlson]

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On 2022-05-12 at 15:36:25, Robert Brown wrote:
> Hi team,

Hey,

> I started a thread in GitHub, but they pointed me to you. We're having a binary comparison problems when cloning a repo in Git on Windows (git version 2.36.1.windows.1), LFS is installed but is not tracking files. 
> 
> So far we have noticed  .gdb, .las, and .loz files are not even close to the same size and don't open after cloning the repo. Everything else seems to clone fine at the moment, confidence to moving to Git is a problem because of this on the team. I'm looking to figure out a way to make sure we are getting binary matched clones when doing so. We sure would appreciate any help you can give us.  

As I mentioned, I think Git LFS is a red herring here.  There are no
patterns in .gitattributes, so the fact that it's installed is
irrelevant, since it's not being used.

To summarize what I said on the Git LFS issue tracker, I think you've
seeing a problem with Git on Windows where it doesn't always handle
files larger than 4 GiB properly.  My guess is that if you created the
repository in WSL or on a Linux box, things would work, provided you
used a 64-bit binary.  Can you try doing that and seeing if cloning to
another Linux-based directory works properly for you in that case?
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]