From: Jeff King <peff@peff.net>
To: Edmundo Carmona Antoranz <eantoranz@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Forcing git to pack objects
Date: Sun, 20 Dec 2015 02:41:07 -0500 [thread overview]
Message-ID: <20151220074106.GE30662@sigill.intra.peff.net> (raw)
In-Reply-To: <CAOc6etZePL=yvy=fVt9e=RmwdStJy6Kf621icYbYOER-NyMvXg@mail.gmail.com>
On Fri, Dec 18, 2015 at 07:03:39PM -0600, Edmundo Carmona Antoranz wrote:
> Recently I was running manually a git gc --prune command (wanted to
> shrink my 2.8G .git directory by getting rid of loose objects) and I
> ended up running out of space on my HD. After freaking out a little
> bit (didn't know if the repo would end up in a 'stable' state), I
> ended up freeing up some space and I again have a working repo...
> _but_ I noticed that basically _all_ objects on my repo are laying
> around in directories .git/objects/00 to ff (and taking a whole lot of
> space... like the .git directory is now like 5 GBs). After running git
> gc manually again it ended up taking a lot of time and the objects are
> still there. Also git svn sometimes gcs after fetching and it took to
> run cause of the gc execution (ended up killing it) and the files are
> still there. Is it possible to ask git to put all those objects in
> .pack files? Or did I mess something on my repo?
It sounds like these objects aren't reachable from any of your refs.
That would explain:
- why they don't get packed; we only pack reachable objects.
There's no easy way with "git gc" or "git repack" to pack unreachable
objects. If you drop down to the "git pack-objects" level, you can
manually convince it to do so.
I have a patch to add "git repack -k", which packs even unreachable
objects (we use this at GitHub, since our routine repository
maintenance never deletes objects). If people are interested, I can
clean it up and post it to the list.
- why your repo grew during the gc; packed unreachable objects are
exploded into loose objects during a gc, so they can age and expire
on their own (we use filesystem mtimes to determine how old they
are).
Git is smart enough not to explode loose objects that it is just
going to prune in a moment. But the default expiration time is 2
weeks, so there's a good chance it would want to keep some of them.
If you use "git gc --prune=now", that should prune everything
immediately (and this is safe, as long as you know there are no
simultaneous users of your local repository).
-Peff
prev parent reply other threads:[~2015-12-20 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-19 1:03 Forcing git to pack objects Edmundo Carmona Antoranz
2015-12-20 2:25 ` Mikael Magnusson
2015-12-20 7:41 ` Jeff King [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=20151220074106.GE30662@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=eantoranz@gmail.com \
--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).