Re: git gc / git repack not removing unused objects?

[Jon Nelson <jnelson@jamponi.net>]

On Fri, Feb 5, 2010 at 3:45 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Fri, 5 Feb 2010, Jon Nelson wrote:
>
>> On Fri, Feb 5, 2010 at 2:51 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
>> > On Fri, 5 Feb 2010, Jon Nelson wrote:
>> >
>> >> [Using git 1.6.4.2]
>> >>
>> >> In one repo I have (136G objects directory, fully packed) I'm having
>> >> some trouble.
>> >> I've run git-gc --prune=now, git repack -Adf, and so on a half-dozen
>> >> times and each time I do so it gets bigger, not smaller.
>> >
>> > Please tell us more.
>>
>> I'll tell you whatever I can -- as soon as I know what it is you want.
>
> I want to know what you did and what results you obtained to lead you to
> believe that 'git-gc --prune=now' makes your repository bigger.

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

Then, just to make sure of some things, I changed nothing and simply
re-ran "git repack -dAl".
After: 167G

Config:

[core]
        repositoryformatversion = 0
        filemode = true
        bare = true
        logallrefupdates = true
        compression = 0
        loosecompression = 0
        packedGitLimit = 1500M
        #packedGitWindowSize = 32m
[pack]
        packsizelimit = 256m
        windowMemory = 128m
        deltaCacheSize = 1m
[gc]
    threads = 1
    packrefs = true

[repack]
        usedeltabaseoffset = true

Incorporating the system and global config (git config -l):

pack.packsizelimit=2M
pack.threads=1
gc.auto=0
gc.autopacklimit=0
core.repositoryformatversion=0
core.filemode=true
core.bare=true
core.logallrefupdates=true
core.compression=0
core.loosecompression=0
core.packedgitlimit=1500M
pack.packsizelimit=256m
pack.windowmemory=128m
pack.deltacachesize=1m
gc.threads=1
gc.packrefs=true
repack.usedeltabaseoffset=true

-- 
Jon