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.
> Setting that aside for the moment, however, I've run into a stranger problem.
>
> So I use "git verify-pack -v > gvp.out" and "sort -k3nr < gvp.out |
> head -n 20" to find the top 20 largest blobs.
> So I have a blob, b32c3d8e8e24d8d3035cf52f606c2873315fe2b8, and now I
> want to know what tree (or trees) it is in, so I try this:
>
>
> for i in $( git branch -a | sed -e 's/\*//g' | grep -v branch ); do if
> git ls-tree -l -r -t $i | grep
> b32c3d8e8e24d8d3035cf52f606c2873315fe2b8 > /dev/null; then echo $i;
> fi; done
>
> The results: no branch or tree appears to contain that blob.
What you did above is simply to list trees that are reachable from the
_heads_ of your branches. If the blob belongs to a commit which isn't
the latest revision of any of your branches then you won't see it like
that.
> So I tried a different approach:
>
> for i in $( grep tree gvp.out | awk '{ print $1 }' ); do if git
> ls-tree $i | grep b32c3d8e8e24d8d3035cf52f606c2873315fe2b8 >
> /dev/null; then echo $i; fi ; done
>
> This time, I find (at least) one tree
> (d813af1537358496ca34958bbff08b87590607bf) with the blob.
> But which branches might that tree appear in? None.
>
> For each branch, I ran "git ls-tree -l -r -t" and saved the output in
> a file (one per branch).
> Then I grepped each file for the tree (
> (d813af1537358496ca34958bbff08b87590607bf) - no luck.
> I grepped each file for the blob (b32...) - no luck.
>
> The results seem to suggest that I have packed trees which reference
> blobs, but that the trees themselves are not referenced in any branch
> and therefore I would expect that they would be pruned.
NO. If those trees and blobs are stil there then they do get
referenced. But not from the latest commit on any of your branches.
You need to dig further down in history to find a commit that actually
references that blob/tree. One easy method is to do:
git log --raw --all
and within the pager ('less' by default) simply search for "b32c3d8".
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html