git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Nelson <jnelson@jamponi.net>
To: unlisted-recipients:; (no To-header on input)
Cc: git@vger.kernel.org
Subject: Re: git gc / git repack not removing unused objects?
Date: Mon, 8 Feb 2010 11:12:03 -0600	[thread overview]
Message-ID: <cccedfc61002080912ybc7775by24fd5511fb67eac5@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1002071937000.1681@xanadu.home>

On Sun, Feb 7, 2010 at 8:11 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
> On Sun, 7 Feb 2010, Jon Nelson wrote:
>> On Sat, Feb 6, 2010 at 7:16 PM, Nicolas Pitre <nico@fluxnic.net> wrote:
>> >On Sat, 6 Feb 2010, Jon Nelson wrote:
>> >>         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).
>
> Why do you synchronize with rsync?  Why not a simple 'git fetch' which
> is likely to be much faster in any case?

Often I need to sync the entire config, and am frequently rsyncing
(although not in this case) rsyncing repos made with git-svn. I've had
trouble using git clone on these repos, as I really want the duplicate
repo to use the svn upstream and not the git repo it was cloned from.

..

> You previously had 2408195 packed objects and after the repack this is
> 2674504.  The difference is 266309, which incidentally is the number of
> objects 'git repack' counted.
>
> If that 266309 object count is stable between repack attempts (and it
> should), then something is failing to clean up the old packs.  If I
> remember right, you were playing with modifications to git-repack.sh
> lately?  It is well possible that you broke it.

Indeedly do I did.

The (now expected) results:

turnip:/mnt/backups.git # du -sh ; echo ; git count-objects -v ; echo
; git repack -ad ; echo ; git count-objects -v ; echo ; du -sh
204G    .

count: 0
size: 0
in-pack: 2939744
packs: 694
size-pack: 213284091
prune-packable: 0
garbage: 0

Counting objects: 266309, done.
Compressing objects: 100% (205176/205176), done.
Writing objects: 100% (266309/266309), done.
Total 266309 (delta 47781), reused 230413 (delta 47770)

count: 0
size: 0
in-pack: 266309
packs: 11
size-pack: 21590451
prune-packable: 0
garbage: 0

21G     .
turnip:/mnt/backups.git #

and of course now everything is nice and (reasonably) fast.
Thanks for the help, and pointing out that the problem was .. me.

-- 
Jon

      reply	other threads:[~2010-02-08 17:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 19:45 git gc / git repack not removing unused objects? Jon Nelson
2010-02-05 20:51 ` Nicolas Pitre
2010-02-05 21:04   ` Jon Nelson
2010-02-05 21:45     ` Nicolas Pitre
2010-02-06 13:53       ` Jon Nelson
2010-02-07  1:16         ` Nicolas Pitre
2010-02-07 17:48           ` Jon Nelson
2010-02-07 23:40             ` Jon Nelson
2010-02-08  2:11               ` Nicolas Pitre
2010-02-08 17:12                 ` Jon Nelson [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cccedfc61002080912ybc7775by24fd5511fb67eac5@mail.gmail.com \
    --to=jnelson@jamponi.net \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).