git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
JNJon Nelson <jnelson@jamponi.net>
Date
Feb 7, 2010, 23:40 UTC
Message-ID
<cccedfc61002071540l7019d5d0mc4666dbd81189064@mail.gmail.com>
In-Reply-To
<cccedfc61002070948m2491b1e2ua633f125f3573ff9@mail.gmail.com>
On Sun, Feb 7, 2010 at 11:48 AM, Jon Nelson <jnelson@jamponi.net> wrote:
Show 43 quoted lines
> On Sat, Feb 6, 2010 at 7:16 PM, Nicolas Pitre <nico@fluxnic.net> 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
The results (two lines of whitespace added for clarity):

turnip:/mnt/backups.git # git count-objects -v ; git repack -ad ; git count-objects -v count: 0 size: 0 in-pack: 2408195 packs: 675 size-pack: 174924053 prune-packable: 0 garbage: 0

Counting objects: 266309, done. Compressing objects: 100% (207820/207820), done. Writing objects: 100% (266309/266309), done. Total 266309 (delta 47751), reused 227730 (delta 45117)

count: 0 size: 0 in-pack: 2674504 packs: 686 size-pack: 196517094 prune-packable: 0 garbage: 0 turnip:/mnt/backups.git # du -sh . 188G . turnip:/mnt/backups.git # find objects -name '*.pack' | wc -l 686 turnip:/mnt/backups.git #

So we went from 136G to 153G to 167G and now 188G.

The oldest .pack file is Jan 29 at 7.0M The pack files vary considerably in size from 220B to 2.0G There are 433 packs that are between 200M and 300M in size. There are 78 packs that are between 500M and 600M in size. There are 211 packs that are less than 256M in size.

I ran "git prune -v --prune=now" and it claims to have removed nothing and the exit status was 0.

I hope this helps!
-- 
Jon
Previous: Jon NelsonNext: Nicolas Pitre
Message 8 of 10 in “git gc / git repack not removing unused objects?”
  1. Jon NelsonFeb 5, 2010
  2. Nicolas PitreFeb 5, 2010
  3. Jon NelsonFeb 5, 2010
  4. Nicolas PitreFeb 5, 2010
  5. Jon NelsonFeb 6, 2010
  6. Nicolas PitreFeb 7, 2010
  7. Jon NelsonFeb 7, 2010
  8. Jon NelsonFeb 7, 2010
  9. Nicolas PitreFeb 8, 2010
  10. Jon NelsonFeb 8, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.