{"thread":{"id":"38643","subject":"assistance with git error","startedAt":"2015-02-24T20:40:56Z","lastAt":"2015-02-24T21:56:58Z","messageCount":3,"participants":["Tom","Jeff King"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"256592","messageId":"loom.20150224T213812-434@post.gmane.org","threadId":"38643","inReplyTo":null,"subject":"assistance with git error","fromName":"Tom","fromEmail":"tdmoretto@hotmail.com","sentAt":"2015-02-24T20:40:56Z","receivedAt":"2015-02-24T20:40:56Z","isPatch":false,"sender":{"key":"tdmoretto@hotmail.com","avatar":null},"body":"Could someone provide me some assistance with troubleshooting the following:\n\nremote: Counting objects: 31654, done.\nerror: pack-objects died of signal 99568/19585)   \nerror: git upload-pack: git-pack-objects died with error.\nfatal: git upload-pack: aborting due to possible repository\ncorruption on the remote side.\nremote: aborting due to possible repository corruption on the remote side.\nfatal: early EOF\nfatal: index-pack failed\n\n\ni know next to nothing about git and was asked to resolve this issue.\n\nthank you.\ntom\n"},{"id":"256595","messageId":"20150224211136.GA32217@peff.net","threadId":"38643","inReplyTo":"loom.20150224T213812-434@post.gmane.org","subject":"Re: assistance with git error","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-02-24T21:11:36Z","receivedAt":"2015-02-24T21:11:36Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Feb 24, 2015 at 08:40:56PM +0000, Tom wrote:\n\n> Could someone provide me some assistance with troubleshooting the following:\n> \n> remote: Counting objects: 31654, done.\n> error: pack-objects died of signal 99568/19585)   \n\nThe output is smushed here due to the use of \"\\r\" for the progress\nreporting, but the interesting message is:\n\n  error: pack-objects died of signal 9\n\nwhich probably overwrote something like:\n\n  remote: Compressing objects:  XXX% (9568/19585)\n\nThe rest of the messages are just the error propagating through the\nvarious programs on the remote and local sides. So something killed\npack-objects with signal 9 (SIGKILL). Just a guess, but it may have been\nkilled for using too much memory.\n\nDo you have control of the server? Is it running Linux? If so, check\nyour system logs to see if the OOM-killer killed it.\n\nIf the server is multi-core, setting:\n\n  git config pack.threads 1\n\nin the repository in question may reduce the peak memory usage.\n\n-Peff\n"},{"id":"256598","messageId":"20150224215658.GA23488@peff.net","threadId":"38643","inReplyTo":"COL127-W7F78AD18199BF6C38EEA0A5160@phx.gbl","subject":"Re: assistance with git error","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2015-02-24T21:56:58Z","receivedAt":"2015-02-24T21:56:58Z","isPatch":false,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Tue, Feb 24, 2015 at 04:49:00PM -0500, Thomas Moretto wrote:\n\n> i also have a question concerning large files.\n\nSure, but let's take it back on-list. Then other people can help answer,\nand later users can benefit from seeing the answers.\n\n> i ran a check and it said there was a schema.sql file that was 1.2G(i followed this guide:  http://stevelorek.com/how-to-shrink-a-git-repository.html)\n\nRunning verify-pack like that is slow. If you have a recent version of\ngit, you can use:\n\n  git rev-list --objects --all |\n  git cat-file --batch-check='%(objectsize:disk) %(objectname) %(rest)' |\n  sort -rn\n\nto get a sorted list of the largest objects that are reachable. If you\ndon't see your big object there, try doing:\n\n  git rev-list --objects --reflog\n\nfor the first line, to see if it shows up in the reflog.\n\nIf the object is only in the reflog, the simplest thing is to expire the\nreflog and repack:\n\n  git reflog expire --expire-unreachable=now --all\n  git gc --prune=now\n\nIf it is reachable, then you'll have to actually rewrite history to get\nrid of it. Since you know the sha1 of the object, you can find which\ncommit introduced it with:\n\n  sha1=...whatever...\n  git log --all --no-abbrev --raw | less +/$sha1\n\nThat will dump you in less, with the sha1 highlighted (if it comes and\ngoes through history, you may need to use \"/\" to find other instances).\n\n-Peff\n"}]}