* Possible git bug when using filter-branch to remove large binaries
@ 2009-02-15 21:35 Juan Zanos
2009-02-15 21:55 ` Thomas Rast
0 siblings, 1 reply; 2+ messages in thread
From: Juan Zanos @ 2009-02-15 21:35 UTC (permalink / raw)
To: git
Hi Vger,
I'm trying to remove a directory of large binaries from a git
repository There is a directory of 85M in a git repository of
92M. So the binaries are relatively massive and should never have
been checked in in the first place. I've tried to use filter-branch
to permanently remove those binaries. The directory successfully
vanishes. However, the repository + working directory only goes from
216M down to 133M. That means the binaries were only removed from
the working directory. The repository remains bloated. I've tried
a handful of magic incantations using commands such as gc, prune,
reflog expire --all, etc.. None of these have worked. In fact,
after cloning the 133M (repo + working) and running gc the directory
actually increased in size from 133M to 290M!
I'm not really sure I understand what's going on here. It sounds
like the growth to 290M is a bug. If so I'm happy to provide the
repo as a test case as well as the exact commands I use. On the
other hand, I'm finding that the git API is complex enough that I
could easily be doing something wrong or missing some command. In
that case is there a simple set of commands I could use to remove a
directory of really large binaries that never should have been
checked in in the first place and reclaim the space ? I've checked
pretty thoroughly on Google to find people who have successfully done
this, but it seems mostly people have failed to actually reclaim space.
Cheers,
Juan
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Possible git bug when using filter-branch to remove large binaries
2009-02-15 21:35 Possible git bug when using filter-branch to remove large binaries Juan Zanos
@ 2009-02-15 21:55 ` Thomas Rast
0 siblings, 0 replies; 2+ messages in thread
From: Thomas Rast @ 2009-02-15 21:55 UTC (permalink / raw)
To: Juan Zanos; +Cc: git
[-- Attachment #1: Type: text/plain, Size: 743 bytes --]
Juan Zanos wrote:
> I'm trying to remove a directory of large binaries from a git
> repository
[...]
> The directory successfully
> vanishes. However, the repository + working directory only goes from
> 216M down to 133M. That means the binaries were only removed from
> the working directory.
We're in fact trying to make a generic recipe and put it in 'man
git-filter-branch'. The preliminary patch is here:
http://article.gmane.org/gmane.comp.version-control.git/109925/
Once you convince your eyes to ignore the leading +, it should be
fairly easy to read in patch form. ;-)
It would be very helpful if you could try the recipe, and report if it
worked.
--
Thomas Rast
trast@{inf,student}.ethz.ch
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-02-15 21:57 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-02-15 21:35 Possible git bug when using filter-branch to remove large binaries Juan Zanos
2009-02-15 21:55 ` Thomas Rast
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.