Re: Bug#813084: Background git gc fails, telling me to run git prune, which doesn't help

From: Ben Hutchings <ben@decadent.org.uk>
Date: Feb 27, 2016, 22:50 UTC
Message-ID: <1456613404.3098.23.camel@decadent.org.uk>
In-Reply-To: <CACsJy8Ai9dW3mLOEidsyh2yw29-2zvYRGB1LZN51B-L4QHMQ2w@mail.gmail.com>

Control: forwarded -1 git@vger.kernel.org

On Fri, 2016-01-29 at 21:05 +0700, Duy Nguyen wrote:

Show 17 quoted lines

> On Fri, Jan 29, 2016 at 8:35 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > git keeps trying to do a background gc on my linux repository, but
> > fails, reporting this in .git/gc.log:
> > 
> > warning: There are too many unreachable loose objects; run 'git prune' to remove them.
> > 
> > However, after running 'git prune' and 'git gc' (which succeeds), git
> > soon tries to a background gc again, resulting in the same error.
> > 
> > Let me know what I can do to get any further diagnostic information.
> 
> Make sure nobody is accessing the repository before you do this:
> 
> git prune --expire=now
> 
> Then you can try "git gc --auto" again to see if it is still
> complaining. Report back on git@vger.kernel.org in that case.

OK, I've now done that and I get the same failure. But 'git gc --prune=all' seems to work:

$ git gc --prune=all Counting objects: 6479254, done. Delta compression using up to 4 threads. Compressing objects: 100% (939232/939232), done. Writing objects: 100% (6479254/6479254), done. Total 6479254 (delta 5503044), reused 6479254 (delta 5503044) Checking connectivity: 6479254, done.

I kept a backup of the .git directory so I can run further experiments on that.

Ben.

-- 
Ben Hutchings
Every program is either trivial or else contains at least one bug