github - Why would git pull stall at the same point while "compressing objects", leading to "corrupt loose object"? -


if git pull after few hours typically stalled pull process can take 10 minutes. after runs pretty (2-3 seconds), until let larger gap go by. notice it's around same objects (3650-3680 in case) , sort of clogs along, 3651... 3652... etc. instead of ripping through them should. once gets 3680ish starts ripping through them again , completes few seconds later.

what recommend? here's printout of latest pull:

counting objects: 6512, done. delta compression using 2 threads. compressing objects:  56% (3677/6463) 

there's 2 of on repository , there's not whole lot of code changes warrant such demanding pull request.

when finish says:

error: corrupt loose object '895fdc42e0015abc74e4cc958393027262374b90' fatal: loose object 895fdc42e0015abc74e4cc958393027262374b90 (stored in /path/to/mysite/.git/objects/89/5fdc42e0015abc74e4cc958393027262374b90) corrupt error: failed run repack 

run git fsck on central repo, , see says. report same object corrupt. find out if it’s referred. if not, delete it. if referred, find out came / might have copy of , replace corrupt object correct copy.


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -