On Sat, Feb 6, 2010 at 7:16 PM, Nicolas Pitre <nico@xxxxxxxxxxx> wrote: > On Sat, 6 Feb 2010, Jon Nelson wrote: > >> Last night, the repo size was 153G after removing some commits and >> objects by way of git filter-branch. >> I'm using "du -sh" in the .git directory to determine the disk usage. >> >> Before: 136G >> git repack -dAl >> After: 153G > > Why are you using -A instead of -a ? As it turns out, I've been using both -a and -A. I suspect -A is a typo on my part. >> Then, just to make sure of some things, I changed nothing and simply >> re-ran "git repack -dAl". >> After: 167G > > Could you run 'git count-objects -v' before and after a repack in such > cases as well? Yes. >> [pack] >> packsizelimit = 256m > > Why are you using this? I didn't want my pack files to be too huge. I've bumped that up to 2G. >> pack.packsizelimit=2M My ~/.gitconfig normally uses 2M for easy rsyncing. In this repo I thought the value was overridden by the project's config (which was specifying 256m and now specifies 2048m). Suboptimal or not, it still doesn't explain why the repo grows with each repack. Now running: git count-objects -v ; git repack -ad ; git count-objects -v -- Jon -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html