That's an older version of git. If you can't avoid doing that, then you may want to try the most recent version of git, and possibly a 64 bit version of git.
Mark Waite On Wednesday, March 9, 2016 at 4:01:01 PM UTC-7, Jerome O'Connor wrote: > > Hi all. > I'm setting up a git repository to help with backing up an archive. The > archive is about 160GB of mostly binary files. I know this isn't the best > use for git, but I'd like to try and get it to work. > The problem I'm getting is that every time I add the files initially, or > then push or clone the directory, I get objects corrupting at random. I > thought it may have been the drives, but testing this on 2 different drives > and 3 different partitions yielded the same results. I also ran a memtest > which didn't pick up any bad RAM. > So what's happened so far: > first init/add/commit, then: > > F:\archived_jobs>git fsck > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 11e4214c0bb2a86605347692bccdebb3be2c4ab6 > error: 11e4214c0bb2a86605347692bccdebb3be2c4ab6: object corrupt or missing > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch ab0314a93ed387193d584f5a49f8cd98d00a75e7 > error: ab0314a93ed387193d584f5a49f8cd98d00a75e7: object corrupt or missing > Checking object directories: 100% (256/256), done. > Checking connectivity: 26094, done. > missing blob ab0314a93ed387193d584f5a49f8cd98d00a75e7 > missing blob 11e4214c0bb2a86605347692bccdebb3be2c4ab6 > > I then moved the .git directory out of the archive and reinitialised and > re-added the repo: > F:\archived_jobs>git fsck > notice: HEAD points to an unborn branch (master) > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 3cdd54f73a2216aea5c67eb94c610472d5410f6d > error: 3cdd54f73a2216aea5c67eb94c610472d5410f6d: object corrupt or missing > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 67f8aa617d3ea57758241399b4d1cf8d051b9f23 > error: 67f8aa617d3ea57758241399b4d1cf8d051b9f23: object corrupt or missing > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 75b9517d49cc538018dba742ac30eb7e5b5b1bd1 > error: 75b9517d49cc538018dba742ac30eb7e5b5b1bd1: object corrupt or missing > Checking object directories: 100% (256/256), done. > notice: No default references > missing blob 75b9517d49cc538018dba742ac30eb7e5b5b1bd1 > missing blob 3cdd54f73a2216aea5c67eb94c610472d5410f6d > missing blob 67f8aa617d3ea57758241399b4d1cf8d051b9f23 > > So corrupt objects again, but DIFFERENT objects. I replace the corrupted > objects with ones from the previous .git directory and git fsck checks out > fine. > I then commit and clone the repo into a bare repo on a different drive, > and run git fsck: > D:\data\repos\archived_jobs>git fsck > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 2da539bdd1e883fe07d0cc7bcab6b2edbaecc9cd > error: 2da539bdd1e883fe07d0cc7bcab6b2edbaecc9cd: object corrupt or missing > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 3dcfdaad5309c2cc22d1c36cb807219802e3cc0e > error: 3dcfdaad5309c2cc22d1c36cb807219802e3cc0e: object corrupt or missing > error: inflate: data stream error (incorrect data check) > error: sha1 mismatch 64671dbf5754312bad99ce73a797aa27243fd734 > error: 64671dbf5754312bad99ce73a797aa27243fd734: object corrupt or missing > Checking object directories: 100% (256/256), done. > Checking connectivity: 26081, done. > missing blob 64671dbf5754312bad99ce73a797aa27243fd734 > missing blob 2da539bdd1e883fe07d0cc7bcab6b2edbaecc9cd > missing blob 3dcfdaad5309c2cc22d1c36cb807219802e3cc0e > > I replace these objects from the initial repo, and fsck gives me no > errors. I then try clone this (using tortoise) to another partition on the > same drive and get: > > git.exe clone --progress -v "D:\data\repos\archived_jobs" > "G:\temp\archived_jobs" > Cloning into 'G:\temp\archived_jobs'... > done. > error: inflate: data stream error (incorrect data check) > error: corrupt loose object 'da8f44c76bb6d08e7a9fd53eb4a594e245e2db8e' > fatal: loose object da8f44c76bb6d08e7a9fd53eb4a594e245e2db8e (stored in > .git/objects/da/8f44c76bb6d08e7a9fd53eb4a594e245e2db8e) is corrupt > 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) (4229296 ms @ 9/03/2016 17:26:19) > > so yeah, 4 separate operations, 9 different corrupted objects. Any ideas > what's happening here and how i can fix it? > I'm running Win7 Ultimate SP1. Drive F: is a 1TB windows software RAID 1. > Drives D: and G: are 1TB partitions on the same 2TB single HDD. > Using TortoiseGit 1.8.11 and > git 1.9.4.msysgit.1 > and the corruption happens regardless of whether i'm using the tortoisegit > gui, or the command line for git > Cheers. Jerome. > > > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
